Skip to main content
Glama

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

Output Schema

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

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and worldview are covered. The description adds meaningful behavioral context: both IDs must be passed together, pagination is supported via page_token, and the warning about not passing a reply's own comment_id goes beyond the schema. It doesn't contradict annotations and adds value without repeating them.

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 single dense paragraph that front-loads the core purpose and then provides usage conditions. It is compact while conveying essential information, but the density of multiple clauses in one sentence makes it slightly less scannable. Nevertheless, it earns its place with no wasted words.

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?

Given the presence of an output schema, the description need not explain return values. It covers the required IDs, usage paths, error-avoidance warnings, and pagination behavior. It is complete for an agent to understand when and how to call this tool, including the edge case of missing IDs and the boundary against sibling tools.

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 extra semantics beyond the schema: it reiterates the requirement to pass both aweme_id and comment_id together, explains when to reuse IDs from first-level results, and forbids passing reply-level comment_ids. This additional guidance, especially the exclusion, elevates it above the schema baseline.

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 (获取/get) and resource (抖音评论回复/comment replies) with required identifiers (aweme_id and comment_id). It clearly distinguishes from sibling tools like douyin_get_video_comments_by_aweme_id (first-level comments) by focusing on replies, and even warns against passing the reply's own comment_id. The purpose is unambiguous and differentiates well.

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?

Provides explicit when-to-use guidance: use directly when the user supplies a valid combination; call the corresponding first-level comment tool to complete missing IDs when the user has an aweme_id, link, or share text; ask the user for video location info if missing. It also explicitly states not to pass the reply's own comment_id, which is a critical usage condition. This fully covers selection and alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation5/5

每个工具都有明确目标且输入变体被清晰描述,如通过不同标识符获取用户信息,通过URL或ID获取评论。虽然存在相似工具,但描述提供了准确使用条件,不会造成混淆。

Naming Consistency5/5

所有工具遵循douyin_或socialdatax_前缀加动作(get/search/submit)加资源的模式,变体后缀(如_by_url、_by_sec_user_id)保持一致,整体命名规则清晰统一。

Tool Count4/5

19个工具对于覆盖用户、视频、评论、搜索和语音转文字等多样化功能流是合理的,虽然数量略多但每个工具在对应场景下都必要,没有过度膨胀。

Completeness4/5

覆盖了数据获取的主要域:用户信息、发布视频、短剧、评论、详情、搜索和独立语音转文字功能。缺少写操作或关注列表等,但作为数据读取MCP其覆盖已相当全面。

Resources