SocialDataX 抖音 Douyin MCP

douyin_get_video_comment_replies_by_comment_id

Read-only

根据 aweme_id 和一级评论 comment_id 获取抖音评论回复；需同时传入 aweme_id 和 comment_id。用户已提供完整合法组合时直接使用；已有 aweme_id、作品链接或分享文案但缺少必需 ID 时，调用对应一级评论工具补全；缺少作品定位信息时向用户索取；不要传回复项自身的 comment_id；支持 page_token 翻页。

Input Schema

TableJSON Schema

Name	Required	Description
`aweme_id`	Yes	抖音作品的数字 aweme_id，通常可从搜索、详情或评论结果中的 aweme_id 字段复用；不要传作品链接、分享文案或带引号的字符串；用户已提供时直接使用；调用评论回复工具时必填，需与 comment_id 同时传入，且两者须属于同一作品
`comment_id`	Yes	一级评论 ID comment_id；用户已提供时直接使用，否则可从一级评论结果 items[].comment_id 复用；调用评论回复工具时必须同时传入同一作品的 aweme_id；不要传评论回复结果里的 items[].comment_id
`page_token`	No	page_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一作品下同一一级评论的回复分页链路，不能跨能力、作品或评论复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	当前页评论回复列表
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`comment_count`	Yes	该一级评论下的回复总量；当前不可用时为 null
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 3, 2026

changedOutput schema / properties / items / items / properties / author / properties / sec_user_id / description

Previous value: -"评论作者 sec_user_id；用户主页工具可直接复用"New value: +"评论作者 sec_user_id；当前不可用时为空字符串"

Changed3 schema fields changedAug 24, 2026

changedInput schema / properties / aweme_id / description

Previous value: -"抖音作品的数字 aweme_id，通常可从搜索、详情或评论结果中的 aweme_id 字段复用；不要传作品链接、分享文案或带引号的字符串；调用评论回复工具时必填，需与 comment_id 同时传入"New value: +"抖音作品的数字 aweme_id，通常可从搜索、详情或评论结果中的 aweme_id 字段复用；不要传作品链接、分享文案或带引号的字符串；用户已提供时直接使用；调用评论回复工具时必填，需与 comment_id 同时传入，且两者须属于同一作品"

changedInput schema / properties / comment_id / description

Previous value: -"一级评论 ID comment_id；可从一级评论结果 items[*].comment_id 复用，用于获取该评论下的回复；调用评论回复工具时必须同时传入 aweme_id"New value: +"一级评论 ID comment_id；用户已提供时直接使用，否则可从一级评论结果 items[*].comment_id 复用；调用评论回复工具时必须同时传入同一作品的 aweme_id；不要传评论回复结果里的 items[*].comment_id"

changedOutput schema / properties / items / items / properties / comment_id / description

Previous value: -"评论 ID"New value: +"当前评论回复自身 ID；不是读取回复时输入的一级评论 comment_id"

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / points

Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "items",
-  "next_page_token",
-  "comment_count"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count",
+  "points"
+]

Changed1 schema field changedJun 8, 2026

changedInput schema / properties / aweme_id / description

Previous value: -"抖音作品 aweme_id；调用评论回复工具时必填，需与 comment_id 同时传入"New value: +"抖音作品的数字 aweme_id，通常可从搜索、详情或评论结果中的 aweme_id 字段复用；不要传作品链接、分享文案或带引号的字符串；调用评论回复工具时必填，需与 comment_id 同时传入"

Changed2 schema fields changedJun 7, 2026

changedInput schema / properties / aweme_id / description

Previous value: -"抖音作品 aweme_id；可从 douyin_search_videos 返回的 items[*].aweme_id、作品详情结果或评论结果中复用"New value: +"抖音作品 aweme_id；调用评论回复工具时必填，需与 comment_id 同时传入"

changedInput schema / properties / comment_id / description

Previous value: -"一级评论 ID comment_id；可从一级评论结果 items[*].comment_id 复用，用于获取该评论下的回复"New value: +"一级评论 ID comment_id；可从一级评论结果 items[*].comment_id 复用，用于获取该评论下的回复；调用评论回复工具时必须同时传入 aweme_id"

Changed2 schema fields changedJun 4, 2026

changedInput schema / properties / page_token / description

Previous value: -"分页令牌。首次请求留空；继续翻页时原样传入上一次返回的 next_page_token；只能用于同一作品下同一一级评论的回复分页链路，不能跨能力、作品或评论复用"New value: +"page_token 是不透明分页令牌。首次请求留空；继续翻页时必须将上一次返回的完整 next_page_token 原样传入，作为 page_token 使用；只能用于同一作品下同一一级评论的回复分页链路，不能跨能力、作品或评论复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"

changedOutput schema / properties / next_page_token / description

Previous value: -"下一页分页令牌；为空表示没有更多结果"New value: +"下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论、关键词或筛选条件复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"

Changed5 schema fields changedMay 29, 2026

changedOutput schema / properties / items / items / properties / content_type / description

Previous value: -"评论内容类型：text 表示文字，image 表示图片，video 表示视频，unknown 表示未知"New value: +"评论内容类型：text 表示文字，image 表示图片，sticker 表示表情或动图，unknown 表示未知"

changedOutput schema / properties / items / items / properties / content_type / enum

Previous value: -[
-  "text",
-  "image",
-  "video",
-  "unknown"
-]New value: +[
+  "text",
+  "image",
+  "sticker",
+  "unknown"
+]

addedOutput schema / properties / items / items / properties / sticker

Added value: +{
+  "anyOf": [
+    {
+      "properties": {
+        "animated_url": {
+          "description": "表情或动图的动态资源链接；不可用时为空字符串",
+          "type": "string"
+        },
+        "static_url": {
+          "description": "表情或动图的静态预览图链接；不可用时为空字符串",
+          "type": "string"
+        }
+      },
+      "required": [
+        "static_url",
+        "animated_url"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "评论表情或动图资源；无表情或动图时为 null"
+}

removedOutput schema / properties / items / items / properties / video_urls

Removed value: -{
-  "description": "评论视频链接列表；无视频时为空数组",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

changedOutput schema / properties / items / items / required

Previous value: -[
-  "comment_id",
-  "aweme_id",
-  "content",
-  "content_type",
-  "create_time",
-  "like_count",
-  "reply_count",
-  "ip_location",
-  "image_urls",
-  "video_urls",
-  "is_hot",
-  "is_folded",
-  "author"
-]New value: +[
+  "comment_id",
+  "aweme_id",
+  "content",
+  "content_type",
+  "create_time",
+  "like_count",
+  "reply_count",
+  "ip_location",
+  "image_urls",
+  "sticker",
+  "is_hot",
+  "is_folded",
+  "author"
+]

AddedMay 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds useful behavioral constraints: both IDs must be supplied together and belong to the same video, reply-level comment_ids must not be passed, and page_token pagination is supported. No mutation or side-effect disclosure is needed given the read-only annotation.

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 a dense single sentence with semicolon-separated guidance, but every clause conveys essential information: core operation, required pairing, fallback path, user interaction, and pagination. It is compact enough for the amount of workflow guidance provided.

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 a read-only paginated lookup tool, the description covers the exact callable precondition, the alternate resolution path, the negative case (reply's own comment_id), and pagination. With an output schema present, no return-format explanation is needed.

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?

The schema already documents all three parameters at 100% coverage, so the baseline applies. The description reinforces important constraints (same-video ownership, not using reply IDs) but adds little parameter-level meaning beyond what the schema property descriptions already contain.

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 the specific operation ('获取抖音评论回复') scoped to a first-level comment_id plus aweme_id, which clearly distinguishes this from siblings like douyin_get_video_comments_by_aweme_id (first-level comments) and URL-based variants. The required ID combination is explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly defines when to call directly (complete valid combination provided), when to fall back to a first-level comment tool to obtain missing IDs, and when to ask the user for missing video-locating information. It also warns not to pass reply-item comment_ids, giving the agent actionable selection and exclusion rules.

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

All SocialDataX 抖音 Douyin MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?