tiktok_list_videosFetch recent TikTok videos visible to your OAuth token. Use cursor and max_count to paginate results, and select JSON or markdown output for easy integration.
List recent TikTok videos visible to the configured OAuth token.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | ||
| max_count | No | ||
| response_format | No | json |
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that the videos are 'recent' and visible to the token, but does not disclose pagination behavior, rate limits, or what 'recent' means. Adequate but not rich.
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 a single concise sentence that efficiently communicates the purpose. It is not verbose, though it could be slightly expanded without losing conciseness.
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 no output schema and undocumented parameters, the description is insufficient. It does not explain the response format, pagination, or what constitutes 'recent'. More detail is needed for a complete understanding.
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 0%, and the description does not mention any parameters. The three parameters (cursor, max_count, response_format) are left unexplained, leaving the agent without guidance on their usage.
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 action 'list', the resource 'TikTok videos', and the scope 'visible to the configured OAuth token'. This distinguishes it from siblings like tiktok_publish_video and tiktok_privacy_audit.
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 does not provide explicit guidance on when to use this tool vs alternatives. No comparison with sibling tools like tiktok_agent_manifest or tiktok_connection_status is given. Usage context is implied but not clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.