Fetch metadata for a sound/track: title, author, duration, and how many videos use it. Use to size a sound's reach before pulling its videos.
| Name | Required | Description | Default |
|---|---|---|---|
| expand | No | Return the full untrimmed payload. Default false = compact JSON. | |
| music_id | Yes | Numeric TikTok music_id |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It states it fetches metadata (read-only), but does not disclose rate limits, auth requirements, or response structure. Adequate for a simple fetch.
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 with no wasted words. First sentence states purpose and outputs; second sentence gives usage hint. Highly efficient.
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 tool simplicity (2 params, no output schema, no annotations), description covers purpose, use case, and key outputs. Lacks response format details but acceptable for a metadata fetch.
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 documentation coverage is 100% for both parameters. Description adds no new meaning beyond schema; e.g., 'music_id' is already described as 'Numeric TikTok music_id'. 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?
The description uses specific verb 'Fetch' and resource 'sound/track metadata', lists returned fields (title, author, duration, usage count), and distinguishes from sibling tiktok_sound_videos by stating 'before pulling its 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?
Provides explicit use case: 'Use to size a sound's reach before pulling its videos.' Implies when to use this tool vs. tiktok_sound_videos. Lacks explicit exclusion of alternatives but clear context.
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.