List a creator's active TikTok Stories (ephemeral posts that expire ~24h). Use to capture story content before it disappears. user_id accepts an @username or numeric id.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of items to return, <=35 | |
| 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?
With no annotations, the description carries full burden. It discloses that stories expire ~24h, implying a time-sensitive fetch. It does not mention rate limits or side effects, but as a read-only operation, this is acceptable.
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 sentences: one for purpose, one for usage, one for parameter. Zero wasted words, front-loaded with essential information.
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?
No output schema, but the description doesn't detail return format. However, for a list tool with few parameters, the description is sufficiently complete to use effectively.
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 that user_id accepts '@username or numeric id', but does not elaborate on count or expand beyond what the schema already provides.
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 verb 'List', the resource 'a creator's active TikTok Stories', and explains what Stories are (ephemeral posts ~24h). This distinguishes it from sibling tools like tiktok_creator_videos which list permanent videos.
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?
Explicitly says 'Use to capture story content before it disappears', giving a clear use case. However, it does not mention when not to use or provide alternatives among sibling tools.
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.