Search live TikTok streams by keyword. Use for real-time/live-content discovery. Paginate with cursor.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | Number of items to return, <=30 | |
| 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. | |
| keyword | Yes | Search query text |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses pagination behavior with 'Paginate with `cursor`.' No annotations are provided, so description carries full burden. It does not address rate limits, empty results, or authorization requirements, but covers basic behavior.
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 sentences, zero waste. Purpose is front-loaded, and key information is presented efficiently.
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 and minimal description. Agent lacks information on return format, error handling, and cursor mechanics beyond basic pagination. Incomplete for confident invocation.
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 covers all 4 parameters with descriptions, achieving 100% coverage. Description adds little beyond schema, such as mentioning count default and cursor usage, but does not significantly enhance understanding.
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?
Description clearly states 'Search live TikTok streams by keyword' and 'Use for real-time/live-content discovery', specifying verb, resource, and domain. This distinguishes from sibling tools like tiktok_search_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 states 'Use for real-time/live-content discovery', providing context. Does not mention when not to use or alternatives, but given the sibling list, the intended use is clear.
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.