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

douyin-ops-mcp

by kungful
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

douyin_comment_publish

Post a new Douyin video comment or reply to an existing comment by providing its comment ID, enabling account-visible engagement through the MCP server.

Instructions

在作品下发一条新评论，或者回复某条已有评论（给 commentId 就是回复）。这是真实对外发言（以使用者账号身份发出），注意语气与频率；一次别连发多条（容易被限流）。不要用于刷评论/导流。

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": {
      "awemeId": "<awemeId>",
      "text": "<text>"
    },
    "name": "douyin_comment_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes评论内容
awemeIdYes作品 ID
commentIdNo要回复的评论 ID（可选）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only carry a title, so the description bears the full burden and it delivers: it says the comment is publicly visible under the user's own account, that tone and frequency matter, and that rapid successive posts risk rate limiting. It stops short of describing failure behavior or what is returned on success, which keeps it from a 5.

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 with zero padding: what it does, how the reply mode is triggered, and the operational risk. The mode-defining detail is front-loaded before the cautions.

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 three-parameter write tool with no output schema and only a title annotation, the description covers the action, the reply mode, public visibility, and throttling risk. The main omission is any statement about login or account prerequisites beyond the passing mention of acting as the user's account.

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 description coverage is 100%, so all three parameters are already documented, including that commentId is the optional ID of the comment being replied to. The description reinforces the commentId behavior but adds no format, length, or content constraints beyond the schema.

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?

The description states a specific verb and resource (post a new comment under a work, or reply to an existing one) and makes the mode switch explicit: supplying commentId means a reply. An agent can distinguish it from read-oriented siblings like douyin_comments_list and douyin_comment_replies without opening any 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?

It gives concrete when-to-use guidance (pass commentId to reply) plus exclusions: do not spam or use for traffic diversion, and do not post multiple comments in a burst. It never names an alternative sibling tool for reading comments, so the routing guidance is clear but not exhaustive.

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