Skip to main content
Glama

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。

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": {
      "post_id": "<post_id>",
      "comment_id": "<comment_id>"
    },
    "name": "tiktok_get_post_comment_replies"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页评论回复列表
pointsYes本次成功调用的积分消耗与账户积分余额。
reply_countYes该一级评论的回复总量;当前不可用时为 null
next_page_tokenYes响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果;非空时必须将完整令牌原样作为下一次请求的 page_token 传回;不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed19 schema fields changed
    • addedOutput schema / properties / items / items / properties / author / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / items / items / properties / author / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / items / items / properties / author / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / items / items / properties / author / properties / tiktok_id / title
      Added value: +"Tiktok Id"
    • addedOutput schema / properties / items / items / properties / author / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / properties / author / title
      Added value: +"TikTokCommentAuthorData"
    • addedOutput schema / properties / items / items / properties / comment_id / title
      Added value: +"Comment Id"
    • addedOutput schema / properties / items / items / properties / content / title
      Added value: +"Content"
    • addedOutput schema / properties / items / items / properties / image_urls / title
      Added value: +"Image Urls"
    • addedOutput schema / properties / items / items / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / items / items / properties / parent_comment_id / title
      Added value: +"Parent Comment Id"
    • addedOutput schema / properties / items / items / properties / post_id / title
      Added value: +"Post Id"
    • addedOutput schema / properties / items / items / properties / publish_time / title
      Added value: +"Publish Time"
    • addedOutput schema / properties / items / items / properties / reply_to_comment_id / title
      Added value: +"Reply To Comment Id"
    • addedOutput schema / properties / items / items / title
      Added value: +"TikTokCommentReplyItemData"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / properties / reply_count / title
      Added value: +"Reply Count"
    • addedOutput schema / title
      Added value: +"TikTokPostCommentRepliesResult"
  4. Changed2 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"分页令牌。首页传空字符串;next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;它是不透明令牌,不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"请求分页令牌是不透明令牌。请求的 page_token 为空字符串表示首页;继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"分页令牌。首页传空字符串;next_page_token 为空字符串表示没有更多结果。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;它是不透明令牌,不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。"New value: +"响应分页令牌是不透明令牌。响应的 next_page_token 为空字符串表示没有更多结果;非空时必须将完整令牌原样作为下一次请求的 page_token 传回;不能修改、截断、脱敏、格式化、重组,也不能跨关键词、筛选条件或不同请求链路复用。"
  5. First observed

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 the safety profile is covered. The description adds genuine context beyond that: it explains the provenance of IDs from a comment list and clarifies the meaning of parent_comment_id and reply_to_comment_id (null when replying directly to the top-level comment), which is non-obvious behavior when reading results.

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?

Front-loaded with purpose, then decision rules, then one clarifying sentence about output fields; every clause carries operational meaning. It is dense but not padded, and the sentence-per-idea structure is easy to scan.

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 output schema exists, return values needn't be described, yet the description still covers the one output ambiguity agents hit (parent_comment_id vs reply_to_comment_id) plus all routing decisions and the pagination token's opaque nature. Nothing needed to invoke it correctly is missing.

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 nonetheless adds disambiguation value beyond the schema by warning that comment_id must be the top-level comment's ID and not a reply item's own ID — a real usage trap the per-parameter text does not state.

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?

States a specific verb and resource (fetch replies of a top-level comment on a TikTok post), scoped by post_id + comment_id, and names pagination support. This clearly distinguishes it from the sibling tools that fetch top-level comments (tiktok_get_post_comments_by_post_id / _by_url).

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?

Explicitly prescribes three routing cases: use directly when a complete valid ID pair is supplied, call the corresponding top-level-comment tool to fill in a missing ID when only post_id or a post URL is available, and ask the user when post locating info is absent. It also states a negative rule (do not pass a reply item's own comment_id), which prevents the most likely misuse.

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.

Resources