TikTok Intelligence ET
ET TikTok Category Trend MCP
Read one page of TikTok category daily trends for a region and date range, optionally filtered by first, second or third-level category IDs.
ET TikTok Category 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 Category Daily Trends
Prompt: Show daily TikTok category trends in [REGION] from [START_DATE] to [END_DATE]. Return the available daily values for the first page.
2. Narrow Trends By Category Level
Prompt: Show the daily trend in [REGION] for [CATEGORY_PATH] over [DATE_RANGE]. Use the matching first-, second-, or third-level IDs that I provide and keep each level distinct.
3. Review A Bounded Trend Period
Prompt: Review at most [PAGE_LIMIT] pages of daily category trends in [REGION] over [DATE_RANGE]. Stop when the returned pagination ends, and do not describe one page as the full period.
What You Need to Provide
Choose a region and date range. Category filters refer to their respective levels; each page is a separate request.
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_category_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-category-trend-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_et_category_trend",
"arguments": {
"endDate": "2026-11-07",
"region": "US",
"startDate": "2026-11-01"
}
}
}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 |
|---|---|---|---|
categoryId | string | optional | Optional category ID. |
categoryL2Id | string | optional | Optional category ID. |
categoryL3Id | string | optional | Optional category ID. |
region | string | required | Two-letter uppercase region. Example: US |
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
How can I inspect TikTok category trends?
Suggested Steps
Workflow example: choose a region and date range, optionally narrow by first-, second-, or third-level category ID, and request pages within a fixed limit. Daily values and pagination must be read from the actual response. No verified trend result is published for this page.
About this sample: Workflow guidance only; no daily metric or complete-period coverage is asserted.
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.