Skip to main content
Glama

douyin_publish_images

Publishes a set of local images as a Douyin image-text post with title, caption, topics, and optional scheduled time; supports dry-run preview.

Instructions

把一组本地图片发布成抖音图文(最多 35 张):标题(≤20 字)、正文、话题、定时发布。同样建议先 dryRun=true 预览截图。图片版权与内容合规由使用者负责。

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": {
      "files": "<files>"
    },
    "name": "douyin_publish_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
descNo正文,可以带 #话题
filesYes本地图片绝对路径数组(jpg/png/webp,按顺序展示)
titleNo标题(≤20 字)
dryRunNotrue = 只填不发布
topicsNo额外话题数组
keepOpenNo停在页面上
scheduleAtNo定时发布时间 "YYYY-MM-DD HH:mm"(可选)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral burden. It does disclose the 35-image cap, the dryRun preview path, scheduling, and shifts content/copyright compliance onto the user, but says nothing about login requirements, what happens on partial failure, or whether publishing is irreversible and public.

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?

Compact and front-loaded: the action and cap come first, then field notes, then the dryRun advice and disclaimer. No filler, though the disclaimer sentence is more legal boilerplate than agent guidance.

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

Completeness3/5

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

For a 7-parameter mutation tool with no output schema and minimal annotations, the description covers the core action but leaves out the post-publish outcome, failure modes, and authentication needs. Adequate minimum, not complete.

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%, so every parameter is already documented, and the description largely restates title length and the dryRun preview. The one genuine addition is the 35-image maximum for files, which is not in the schema.

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?

States a specific verb and resource: publish a set of local images as a Douyin image-text post, with a hard cap of 35 images. The image-text framing implicitly separates it from douyin_publish_video, though it never names that 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 Guidelines3/5

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

Recommends running with dryRun=true first to preview screenshots, which is real workflow guidance. However, it gives no when-not guidance, no alternatives, and no stated prerequisites such as being logged in.

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