Skip to main content
Glama
Sign In
douyin-mcp-server

douyin-mcp-server

by maplezhang123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

parse_douyin_video_info

Extract a Douyin video’s ID, title, download URL, and parsing method from a share link to retrieve metadata and download details.

Instructions

解析视频 ID、标题、下载地址与解析方式。

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": {
      "share_link": "<share_link>"
    },
    "name": "parse_douyin_video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_linkYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about network fetch behavior, failure modes for invalid or expired share links, rate limits, or whether parsing is local vs remote. It only lists outputs, which the output schema already covers.

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?

A single compact sentence with no filler, front-loading the action verb and the field list. It is efficient, though the brevity is partly under-specification rather than discipline.

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

Completeness2/5

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

An output schema exists, so return values need not be re-explained, but the description leaves the only input parameter undocumented and offers no guidance on the tool's place among three overlapping siblings. For a network-fetch parsing tool this is thin.

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

Parameters2/5

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

The single required parameter share_link has 0% schema description coverage and is never mentioned in the description. The description enumerates outputs, not the input, so nothing compensates for the undocumented parameter — the agent must guess whether it accepts a full URL, a share code, or plain text.

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

Purpose4/5

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

The verb '解析' (parse) plus the explicit enumeration of extracted fields (视频 ID、标题、下载地址、解析方式) makes the purpose concrete. However, it never distinguishes itself from the similar siblings extract_douyin_text or get_douyin_download_link, which clearly overlap in scope.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus its siblings, nor any precondition about the share link format. An agent seeing four Douyin-related tools gets no routing guidance from this description.

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

Deploy Server

Other Tools