List a creator's followers (paginated). Use for audience mapping and finding connected accounts. Paginate with cursor.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of items to return, <=50 | |
| cursor | No | Pagination cursor — pass the `cursor`/`max_cursor`/`has_more` value from a prior response. | |
| expand | No | Return the full untrimmed payload. Default false = compact JSON. | |
| user_id | Yes | @username or numeric user_id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It implies a read-only operation ('list'), but does not disclose auth needs, rate limits, or behavior for private creators. Adequate but not detailed.
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?
Two concise sentences, front-loaded with purpose. No wasted words.
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?
Tool is simple; description covers purpose, pagination, and a usage hint. No output schema, but the behavior is straightforward. Could mention return format but not essential.
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%, so baseline is 3. The description adds 'Paginate with cursor' which is already in schema. No additional semantic enrichment beyond schema.
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 'List a creator's followers (paginated)', providing a specific verb and resource. It distinguishes from siblings like tiktok_creator_following (which lists who the creator follows) and other audience-related tools.
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 clear usage context: 'Use for audience mapping and finding connected accounts' and mentions pagination with cursor. However, it does not explicitly state when not to use or mention alternatives.
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.
Each tool targets a distinct data type or action (creator, video, comment, sound, hashtag, search, etc.) with no functional overlap. Agents can easily distinguish them based on their clear entity-action pairing.
All tools follow a 'tiktok_' prefix and a consistent noun-first pattern (e.g., 'tiktok_creator_profile', 'tiktok_video_stats'), but there is a minor inconsistency between 'creator' and 'user' for the same entity (e.g., 'tiktok_user_stories' vs 'tiktok_creator_profile').
At 19 tools, the count is slightly high but justified by the breadth of TikTok's public data surface (profiles, videos, comments, sounds, hashtags, searches, etc.). Each tool serves a specific purpose, and the set feels comprehensive rather than bloated.
The tool set covers most read-only operations for TikTok public data, including profiles, videos, comments, sounds, hashtags, and searches. Missing are direct trending feeds or aggregated analytics, but search capabilities compensate. No create/update/delete exists, which is expected for a data extraction server.