Fetch TikTok explore videos for a selected category. Pass the category type ID from the category endpoint to return that category's explore feed.
Retrieve the TikTok explore feed for a category. Returns explore videos for a TikTok category id from the category endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Category type id returned by the category endpoint |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, yet the description fails to disclose behavioral traits such as pagination, rate limits, error handling for invalid IDs, or authentication requirements. The description simply states the return type without fuller behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences long with no extraneous information. It efficiently explains the tool's purpose and parameter dependency.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description adequately conveys the basic purpose and parameter source. However, it lacks details on response structure, error conditions, and usage limitations, which would help complete the picture for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the schema description already explains that 'id' is a category type id from the category endpoint. The description adds minimal additional value by mentioning it retrieves explore videos, but does not elaborate on valid id values or formatting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves the TikTok explore feed for a category and returns explore videos. It specifies the resource (explore feed for a category) and the action (retrieve), distinguishing it from sibling tools like tiktok_category or tiktok_trending.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The description does not mention when to choose tiktok_explore over tiktok_trending, tiktok_category, or other TikTok tools, leaving the agent without context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.