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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_transcribe

Transcribe spoken content from Douyin video/audio links or local files into text, optionally with timestamps, using automatic backend fallback for subtitle drafts and viral script analysis.

Instructions

把视频/音频里的口播转成文字（可带时间轴）。三级降级：硅基流动 SenseVoice（快、便宜）→ 阿里云百炼 qwen3-asr → 本地 faster-whisper（离线免费，首次要下模型）。用于拆解爆款口播结构、给自己拍的口播生成字幕稿。

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": {
      "target": "<target>"
    },
    "name": "douyin_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
engineNo识别后端，默认 auto
targetYes抖音作品链接 / 作品 ID / 本地音视频文件路径
saveDirNo临时文件目录（默认 data/downloads）
segmentsNo是否返回带时间轴的分段（默认 false）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations carry only a title, so the description must supply the behavior, and it does: a three-tier fallback chain with the cost/latency tradeoff of each tier and the setup cost of the local backend ('首次要下模型'). That is meaningful operational context. It does not mention API-key or auth needs for SiliconFlow/DashScope, nor whether the video is downloaded first.

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

Conciseness5/5

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

Three short clauses: what it does, how it degrades, why you'd use it. The purpose is front-loaded and every clause adds information with no 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?

For a 4-parameter tool with no output schema, the description covers function, backend behavior, and the optional timeline output. It leaves the actual return shape (raw text vs. segment objects) and whether a transcript file lands in saveDir unstated, which is a minor gap rather than a blocking one.

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

Parameters5/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the ordering of the 'auto' enum value across the three backends. Combined with '可带时间轴' explaining the segments toggle, it adds real meaning beyond the schema 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 description gives a concrete verb and resource ('把视频/音频里的口播转成文字'), plus scope detail (optional timeline) and two named use cases. That is enough to separate it from douyin_parse and douyin_download without opening schemas, though it never names a sibling explicitly.

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?

It names two concrete situations where the tool fits ('拆解爆款口播结构', '给自己拍的口播生成字幕稿'), which is real when-to-use context. It does not state exclusions or point to alternatives, so it stops short of a 5.

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