TikTok Intelligence ET
ET TikTok Influencer Trend MCP
Read one page of daily TikTok influencer trends for a user ID within the most recent 180 days, including followers, engagement and estimated sales.
ET TikTok Influencer Trend AI Prompts & Use Cases
After connecting this MCP tool to your AI assistant, you can ask the questions below. Replace bracketed placeholders with your own inputs and use the supported values in Arguments.
New to Nexscope MCP? Follow the connection guide, then use the prompts below. The Integration and Parameters & Response tabs contain the connection steps, call example, and technical reference.
1. Review Influencer Daily Activity
Prompt: Show the daily trend for TikTok influencer [USER_ID] from [START_DATE] to [END_DATE], within the last 180 days. Summarize only the returned follower, engagement, and estimated sales fields.
2. Collect A Bounded Trend Window
Prompt: Review at most [PAGE_LIMIT] pages of the daily trend for influencer [USER_ID] over [DATE_RANGE]. Keep the date range within the last 180 days and stop at the returned final page.
What You Need to Provide
Provide one influencer user ID and a range within the most recent 180 days. Page through results only within a requested limit.
Step 1 · Connect
Connect Your AI Assistant
Connect a compatible MCP client to Nexscope, then select this tool from your assistant. Use the connection settings in your client to complete authentication.
POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/jsonAuthentication
Use OAuth 2.1 Authorization Code with PKCE and the mcp:tools scope. API keys remain supported as a compatibility option.
Authorization: Bearer nk-xxxxxxxxxxxxxxxxxUsing an API key? Get your key from API Access and include it in the Authorization header shown above.
Call this MCP tool
nexscope_data_et_influencer_trendhttps://api.nexscope.ai/mcptools/callInitialize an MCP 2025-11-25 Streamable HTTP session at https://api.nexscope.ai/mcp, then use tools/call.
{
"jsonrpc": "2.0",
"id": "tiktok-influencer-trend-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_et_influencer_trend",
"arguments": {
"endDate": "2026-11-07",
"startDate": "2026-11-01",
"userId": "6787875411281134598"
}
}
}MCP 2025-11-25 · Streamable HTTPProgress is delivered on the original POST SSE response. GET SSE carries notifications; reconnecting must query existing asynchronous work rather than submit again.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
userId | string | required | Influencer numeric ID. Example: 6787875411281134598 |
startDate | string | required | Start date, yyyy-MM-dd. Example: 2026-11-01 |
endDate | string | required | End date, yyyy-MM-dd. Example: 2026-11-07 |
pageNum | integer | optional | One page per call. |
pageSize | integer | optional | Records per page, at most 10. |
Response fields
Treat structuredContent as the programmatic API response payload.
| Name | Type | Required | Description |
|---|---|---|---|
data | array | optional | - |
errcode | integer | required | - |
Workflow Guide
Workflow example, not a verified API response.
Your Goal
What period can an influencer trend request cover?
Suggested Steps
Workflow example: provide one influencer user ID and dates within the most recent 180 days, then review the returned daily records page by page within a chosen limit. Estimated sales are not confirmed transactions. No verified trend response is published for this page.
About this sample: Workflow guidance only; no current influencer metrics are shown.
Published sample data is not available for this page. A format illustration or workflow guide is not a substitute for a published result.
View the MCP Request & Response Format
Examples
Workflow example, not a verified API response.
The JSON-RPC envelope below illustrates how the shown arguments and payload fit into MCP. It is not captured network traffic or proof of a successful call. Workflow-only examples do not include a result.
MCP Request
No verified MCP request example is available. Refer to Integration and the documented requirements before preparing a call.
MCP Response Format
This workflow does not claim an API result. No verified response example is available; refer to Parameters & Response for the documented response structure.