Retrieve TikTok video metadata and automatically download the video file to your local device.
Fetch TikTok video metadata including description, author info, and video download URL. Automatically downloads the video via the browser extension and saves it locally.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | TikTok video URL | |
| savePath | No | Local path to save the video file. Defaults to ~/Downloads/tiktok_{video_id}.mp4 |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the behavioral burden. It discloses that the tool automatically downloads the video via the browser extension and saves it locally, which is important. However, it doesn't mention permissions, rate limits, or what happens if the download fails. Some behavioral context is provided but incomplete.
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 the main purpose. No wasted words, but slightly redundant: 'video download URL' and 'downloads the video' could be streamlined.
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, so the description should explain return values, but it only lists metadata fields briefly. It mentions description, author info, and download URL, but not other metadata that might be returned. The behavioral aspect of downloading is covered, but the completeness is moderate.
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 the schema already documents both parameters. The description does not add any parameter-specific meaning beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.
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 a specific verb+resource: fetching TikTok video metadata (description, author info, download URL). It also adds that the tool downloads and saves the video. However, it doesn't differentiate from siblings like fetch_wechat_article or fetch_xiaohongshu_note other than by platform, which is adequate but not exceptional.
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?
No explicit when-to-use or when-not-to-use guidance. The description implies it's for retrieving TikTok video data, but doesn't mention alternatives or conditions. Implied usage only.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.