TikTok Intelligence ET
ET TikTok Level 3 Categories MCP
List TikTok third-level product categories in a selected language, optionally under a known second-level category ID returned by the category list.
ET TikTok Level 3 Categories 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. Browse Third-Level Categories
Prompt: List third-level TikTok product categories in [LANGUAGE]. Show the available names and IDs without assuming a parent.
2. Explore One Second-Level Category
Prompt: Show third-level TikTok categories under second-level ID [PARENT_ID] in [LANGUAGE]. Use an ID returned by the second-level list.
What You Need to Provide
Use a real second-level parent ID when narrowing the list. Language controls the returned labels.
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_l3https://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-level-3-1",
"method": "tools/call",
"params": {
"name": "nexscope_data_et_category_l3",
"arguments": {
"language": "en-US",
"parentId": "851848"
}
}
}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 |
|---|---|---|---|
language | string | required | Response language. Example: en-US |
parentId | string | optional | Parent category ID. Example: 851848 |
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
Which parent ID should I use for third-level categories?
Suggested Steps
Workflow example: request the second-level dictionary, select a returned second-level ID, and use it as the parent filter here. A top-level ID is not a substitute. No verified third-level result is published for this page.
About this sample: Workflow guidance only; the exact child categories depend on the selected parent and response.
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.