List videos on the connected TikTok account. Returns id, title, share_url, view/like/comment/share counts. Paginate via cursor.
| Name | Required | Description | Default |
|---|---|---|---|
| cursor | No | Pagination cursor from a previous call's `cursor`. Omit for the first page. | |
| max_count | No | Page size, 1-20. Default 20. | |
| in_workspace | No | Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected. |
Changes observed during successful MCP inspections.
Input schema / properties / in_workspaceAdded value: +{
+ "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+ "type": "integer"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is fully covered structurally. The description adds only that it returns specific fields and paginates via cursor, which is modest additional context rather than rich behavioral disclosure.
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?
Three short, front-loaded sentences: purpose, return shape, and pagination. No filler, and the primary purpose leads.
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?
With no output schema, the description usefully compensates by enumerating the returned fields (id, title, share_url, counts) and explaining pagination, which is enough for correct invocation. Only minor gaps remain, such as ordering or rate/scope limits.
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 all three parameters (cursor, max_count, in_workspace) are already documented in the schema. The description's only parameter-related content is 'Paginate via cursor,' which adds nothing beyond the schema's cursor field description. Baseline 3 is appropriate.
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?
States a specific verb (List) and resource (videos) with the scope narrowed to 'the connected TikTok account' and the platform named, which cleanly separates it from youtube_list_videos, instagram_list_media, and tiktok_account_stats. An agent can identify the tool without opening the schema.
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 implies its listing role and gives one usage hint ('Paginate via cursor'), but never states when to prefer it over siblings or any precondition (e.g., connected account state). Usage is inferable rather than explicitly guided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.