tiktok-video-downloader
Downloads TikTok videos directly from a video URL. Submit a valid TikTok video link to retrieve the video file.
Instructions
根据视频链接下载TikTok视频
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | TikTok视频链接 |
Downloads TikTok videos directly from a video URL. Submit a valid TikTok video link to retrieve the video file.
根据视频链接下载TikTok视频
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | TikTok视频链接 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only restates the core action of downloading a video and gives no details about output format, whether it returns a file path or URL, potential failures, authentication requirements, or platform restrictions. This is a significant transparency gap.
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?
The description is a single front-loaded sentence with no wasted words; it directly communicates verb, object, and input. However, it is somewhat terse and borderline under-specified, which keeps it just below a perfect score.
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?
For a simple single-parameter tool, the description is minimally adequate: the action and the required input are clear. But with no output schema and no annotations, the tool's expected result or behavior after invocation is not explained, leaving an agent to guess what the response will contain.
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?
The schema already has 100% coverage with the parameter description 'TikTok视频链接', so the baseline is 3. The description adds no additional parameter meaning beyond reinforcing that the URL must be a TikTok video link; it does not clarify allowed URL formats or whether share links are accepted.
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 states a specific verb ('下载' / download), a specific resource ('TikTok视频'), and the input condition ('根据视频链接' / based on a video link). It clearly differentiates from sibling video downloaders for other platforms like bilibili, youtube, or xiaohongshu by naming TikTok explicitly.
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 implies when to use the tool: when a user provides a TikTok video link and wants it downloaded. However, it provides no explicit guidance about when not to use it, nor does it reference any alternative sibling tool, so the usage context is only implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.