Skip to main content
Glama

DouParse - Short Video Link Parser

parse_video

Read-only

Parse a short-video or image-post share link and return watermark-free direct URLs.

解析短视频/图文分享链接,返回无水印直链。

支持平台:抖音、快手、小红书、哔哩哔哩、微信视频号、微博、知乎等。
参数 url 可以是分享文本(含口令的整段文字)、短链(如 https://v.douyin.com/xxx/)
或完整链接。返回字段见下:视频类看 video_url / qualities,图集类看 images,
背景音乐看 music_url:抖音原声 MP3 直链,服务端在解析时已用 music_mid 换好并
回填,可直接下载;music_url 为空说明该平台没有独立音频文件或版权受限。
视频 / 图片直链有时效,过期重解析;音频是静态 MP3,通常长期有效。

Args:
    url: 分享文本、短链或完整视频/图文链接。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "parse_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes分享文本、短链或完整视频/图文链接。Share text, a short link, or a full post URL.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/openWorld/non-idempotent/non-destructive; the description adds real behavior beyond them – output URLs are time-limited and stale results must be re-parsed, which explains the non-idempotent hint, and an empty music_url signals no standalone audio or licensing limits. It doesn't mention auth or rate limits, but those are not implied by this tool's shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and result, then platform list, input forms, and per-field return guidance in a scannable order. The English and Chinese blocks repeat the same content, which is mild redundancy, though the field notes are substantive rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers platforms, accepted input forms, where to read results per media type, and link-expiry behavior – complete for a one-parameter parse tool with an output schema. The per-field notes partly duplicate the output schema, so it isn't maximally tight.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single url parameter is already documented in the schema with the same 'share text / short link / full URL' wording. The description only marginally enriches it by noting share text may contain a code word, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Parse a short-video or image-post share link') plus the outcome ('return watermark-free direct URLs'), and lists the supported platforms. The purpose is unambiguous even though the siblings (get_balance, redeem_code) are unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains accepted input shapes (share text with code word, short link, full URL) and gives operational guidance: links expire so re-parse, audio MP3 is long-lived. It stops short of explicit when-not-to-use conditions, and there are no relevant alternatives among siblings to route to.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.