Retrieve top-level comments from a TikTok video using its ID. Supports cursor-based pagination to fetch additional comments.
Retrieve TikTok video comments. Returns top-level TikTok video comments with cursor-based pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Pagination cursor | |
| aweme_id | Yes | TikTok video id from the video URL |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It mentions cursor-based pagination and that it returns top-level comments, but does not cover potential limitations, sorting, or whether authentication is needed. This is adequate but not thorough.
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 extremely concise with two sentences that front-load the core purpose. Every sentence adds value, with no redundancy or fluff.
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 low complexity and absence of an output schema, the description should hint at the return data structure (e.g., comment fields). It only mentions 'top-level comments' and pagination, leaving users uninformed about what is actually returned. This is a significant gap.
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 description coverage is 100%, so the baseline is 3. The description adds minimal value beyond the schema, merely reinforcing that the id comes from a video URL and that cursor is for pagination. No new meaning is added.
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 the tool retrieves TikTok video comments, specifically top-level ones, and mentions cursor-based pagination. It effectively distinguishes from sibling tools like tiktok_post, tiktok_search, etc., by specifying its unique function.
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?
The description provides no guidance on when to use this tool versus alternatives. It lacks information about prerequisites, exclusions, or scenarios where other tools might be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.