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

douyin-mcp-server

by maplezhang123
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

extract_douyin_text

Extract transcripts from Douyin videos using the share link. Use cloud transcription with an API key or local offline mode.

Instructions

提取文案。cloud 需要 SILICONFLOW_API_KEY；local 是可选离线模式。

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": "extract_douyin_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctxNo
contextNorewrite
asr_modeNocloud
share_linkYes
local_modelNosmall

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that cloud mode requires SILICONFLOW_API_KEY and that local mode is an optional offline mode. However, it omits other important behavior such as extraction output format, failure conditions, or limits.

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?

The description is two short clauses and is front-loaded with the core action before mode details. It is concise, though its extreme brevity reflects under-specification rather than optimal restraint.

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?

For a five-parameter tool with no annotations and 0% schema description coverage, the description is incomplete. Output schema exists, so return values need not be explained, but parameter meaning and usage context are still missing.

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?

Schema description coverage is 0% for five parameters, so the description must explain them. It loosely maps to asr_mode's cloud/local values but never names or explains share_link, context, asr_mode, or local_model. The compensation is far from sufficient.

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

Purpose3/5

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

The description says '提取文案' (extract text/copy), which gives a verb+object but does not specify that it extracts text from a Douyin share link. It does not distinguish this tool from siblings like recognize_audio_file or parse_douyin_video_info. The mode note helps but remains vague about the exact resource.

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?

It mentions cloud vs. local mode and the API-key requirement for cloud, but gives no guidance on when to choose this tool over alternatives. No when-to-use or when-not-to-use guidance is provided relative to sibling tools.

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