SocialDataX TikTok MCP

tiktok_get_post_comment_replies

Read-only

根据 TikTok 作品 post_id 和一级评论 comment_id 获取回复，支持 page_token 翻页。用户已提供完整合法的 ID 组合时直接使用；已有 post_id 或作品链接但缺少必需 ID 时，调用对应一级评论工具补全；缺少作品定位信息时向用户索取；不要传回复项自身的 comment_id。回复项的 parent_comment_id 表示所属一级评论，reply_to_comment_id 直接回复一级评论时为 null。

Input Schema

TableJSON Schema

Name	Required	Description
`post_id`	Yes	TikTok 作品 post_id；用户已提供时直接使用，否则可使用 tiktok_search_posts 返回的 content_type=video 或 image 的 post_id；读取评论回复时也可使用评论列表 items[*].post_id；长数字字符串，原样传入，不要转为数字
`comment_id`	Yes	TikTok 一级评论的数字 comment_id；用户已提供时直接使用，否则来自评论列表 items[*].comment_id；长数字字符串，原样传入，不要转为数字
`page_token`	No	分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes	当前页评论回复列表
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`reply_count`	Yes	该一级评论的回复总量；当前不可用时为 null
`next_page_token`	Yes	分页令牌。首页传空字符串；next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；它是不透明令牌，不能修改、截断、脱敏、格式化、重组，也不能跨关键词、筛选条件或不同请求链路复用。

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses pagination behavior, the need for a complete post_id/comment_id pair, how to source missing IDs, and the semantics of parent_comment_id and reply_to_comment_id in the response. It also adds the caution against using a reply-level comment_id as input, which is valuable operational context not covered by the annotations.

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 description is compact, front-loaded with the core purpose, and every sentence contributes either to ID resolution, pagination, or field semantics. No filler or repetitive material is present.

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 tool's complexity and the presence of an output schema, the description covers everything needed to call it correctly: how to obtain post_id and comment_id, when to ask the user, how to page, and how to interpret reply relationships. It also proactively prevents a likely misuse with the '不要传回复项自身的 comment_id' instruction.

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 schema already documents the three parameters in detail. The description adds meaningful clarification that comment_id must be a first-level comment, not a reply's own comment_id, and reinforces the pagination flow with page_token. It does not fully duplicate the schema and contributes extra semantic guidance.

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: '根据 TikTok 作品 post_id 和一级评论 comment_id 获取回复' (get replies for a first-level comment on a TikTok post). It explicitly distinguishes itself from the first-level comment tools by using '一级评论' and describing reply retrieval, clearly separating it from sibling tools like tiktok_get_post_comments_by_post_id.

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?

The description gives explicit routing instructions: use directly when a valid ID pair exists, call the corresponding first-level comment tool when IDs are missing, and ask the user when post locating information is absent. It also warns not to pass the reply item's own comment_id, providing clear when-to-use and when-not-to-use guidance.

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

All SocialDataX TikTok MCP tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, though several are pairs differentiated only by input type (URL vs ID) such as get_post_comments_by_url/by_post_id and get_user_info_by_profile_url/by_tiktok_id. These pairs are described clearly so an agent can tell them apart, but the similarity could cause occasional misselection.

Naming Consistency4/5

The naming generally follows a consistent pattern of tiktok_ + verb + resource + explicit by_* suffix, with clear verbs like get, search, and submit. However, the socialdatax_get_points_balance tool breaks the 'tiktok_' prefix convention, and the speech text tools mix 'job' and 'by_' in less uniform ways, creating minor inconsistencies.

Tool Count5/5

With 13 tools, the server covers a comprehensive set of TikTok data operations (user info, posts, comments, replies, search, speech transcription, and account balance) without becoming unwieldy. Each tool serves a distinct need, and the count is well within the ideal range for a focused API integration.

Completeness4/5

The tool surface covers major workflows like fetching user info, posts, comments, replies, searching, and handling speech-to-text jobs. The primary gap is the lack of a get_post_detail_by_post_id tool when post_id is available, which would complement the existing comment and search tools and could be needed for direct post lookups.

Resources

Need Help?