wechat-video-downloader
Paste a WeChat Channels video link to download the video file directly.
Instructions
根据链接下载视频号视频
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 视频号链接 |
Paste a WeChat Channels video link to download the video file directly.
根据链接下载视频号视频
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | 视频号链接 |
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?
With no annotations, the description carries the full burden, but it only states the download action. It does not describe the return value, whether saving/auth is involved, or failure modes, which leaves a substantial gap for an agent that must predict the tool's 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?
A single short sentence with no filler; the action and resource are front-loaded. It is appropriately concise for a one-parameter tool.
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?
Despite the low complexity, the description omits what the tool returns after downloading and any conditions on the link (e.g., accessibility or authorization). With no output schema and no annotations, an agent does not have enough information to know how to interpret the call result.
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 description coverage is 100%: the url parameter is already described as '视频号链接'. The description adds no further meaning about link format, examples, or constraints, so a 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 names a specific verb (下载/download) and a specific resource (视频号视频/WeChat Channels video), making the tool's purpose immediately clear. This also distinguishes it from sibling video downloaders for other platforms such as instagram-video-downloader and youtube-video-downloader.
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 guidance is given about when to choose this tool over alternatives like wechat-channels-crawler or the other platform-specific downloaders, and no prerequisites or exclusions are stated. The only hint is the implicit condition of having a 视频号 link, which is already visible from the required url parameter.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.