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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_publish_video

Publish local videos to Douyin via creator center with titles, descriptions, topics, custom covers, and scheduled posting. Use dry-run to preview the filled publish page and screenshot before going live.

Instructions

把本地视频发布到抖音（走创作者中心真实上传流程）：标题、正文、话题、自定义封面、定时发布。强烈建议先用 dryRun=true 走一遍：它会一路填到"发布按钮就在眼前"并截图，确认无误再 dryRun=false 真发。需要先 douyin_login_qrcode 登录。注意：发布内容的合规性（是否原创/是否侵权/是否符合平台规则）由使用者负责，只会发到使用者本人账号。

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": {
      "file": "<file>"
    },
    "name": "douyin_publish_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo正文/简介，可以带 #话题
fileYes本地视频文件绝对路径（mp4/mov，≥3 秒，建议 9:16）
coverNo自定义封面图片路径（可选）
titleNo作品标题（≤30 字，可留空）
dryRunNotrue = 只填不发布，返回预览截图（建议第一次这么用）
topicsNo额外话题数组，不带 # 号，例如 ["职场干货","副业"]
keepOpenNo停在页面上不要关闭（人可以接手补信息）
scheduleAtNo定时发布时间，格式 "YYYY-MM-DD HH:mm"（可选，最多提前 14 天）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations carry essentially no behavioral information (only a title), so the description bears the full burden and delivers: it discloses that this is a real browser-driven upload, that dryRun fills everything up to the publish button and returns a screenshot, that publishing goes only to the caller's own account, and that content-compliance responsibility sits with the user. It still does not say whether a real publish is irreversible/public or what happens on mid-flow failure.

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?

The scope sentence, the recommended dry-run workflow, the login prerequisite and the responsibility caveat all appear in that order with no filler. Every sentence carries actionable information for an agent.

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

Completeness5/5

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

For an 8-parameter mutation tool with no output schema, the description covers purpose, prerequisite, safe-preview path, account scoping and liability, which is everything an agent needs before invoking. Nothing essential is left implicit.

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

Parameters4/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; the description adds genuine meaning beyond it by explaining what dryRun actually does mechanically ('一路填到发布按钮就在眼前并截图') rather than just 'preview'. The remaining parameters (title, desc, topics, cover, scheduleAt) are only listed, adding little over the schema's own descriptions.

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 ('把本地视频发布到抖音') and enumerates the supported surfaces (标题、正文、话题、自定义封面、定时发布), plus disambiguates from douyin_publish_images by saying it goes through the creator-center real upload flow. An agent can identify exactly what this does without opening the schema.

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?

Gives an explicit recommended workflow (先用 dryRun=true 走一遍，确认无误再 dryRun=false 真发) and a hard prerequisite (需要先 douyin_login_qrcode 登录). It does not mention the sibling douyin_publish_preflight or contrast itself with douyin_publish_images, so the alternative-selection guidance is incomplete rather than absent.

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