Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

kuaishou_get_video_comment_replies_by_comment_id

Read-only

根据 photo_id 和一级评论 comment_id 获取评论回复;用户已提供完整合法的 ID 组合时直接使用;已有 photo_id、作品链接或分享文案但缺少必需 ID 时,调用对应一级评论工具补全;缺少作品定位信息时向用户索取;不要传回复项的 comment_id。

Input Schema

NameRequiredDescriptionDefault
photo_idYes快手作品 photo_id;用户已提供时直接使用,否则可从包含 photo_id 的快手作品结果中复用。
comment_idYes一级评论 ID;用户已提供时直接使用,否则可从一级评论结果 items[].comment_id 复制;用于获取该评论下的回复;不要传回复项的 comment_id。
page_tokenNo回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一作品下同一一级评论的回复分页链路,不能跨能力、作品或评论复用。

Output Schema

NameRequiredDescriptionDefault
itemsYes当前页评论回复列表。
pointsYes本次成功调用的积分消耗与账户积分余额。
next_page_tokenYes下一页不透明分页令牌;为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_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. Changed16 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 / user_id / title
      Added value: +"User Id"
    • addedOutput schema / properties / items / items / properties / author / title
      Added value: +"KuaishouCommentAuthorData"
    • 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 / create_time / title
      Added value: +"Create Time"
    • addedOutput schema / properties / items / items / properties / like_count / title
      Added value: +"Like Count"
    • addedOutput schema / properties / items / items / properties / photo_id / title
      Added value: +"Photo Id"
    • addedOutput schema / properties / items / items / properties / reply_to_user_id / title
      Added value: +"Reply To User Id"
    • addedOutput schema / properties / items / items / properties / reply_to_user_name / title
      Added value: +"Reply To User Name"
    • addedOutput schema / properties / items / items / title
      Added value: +"KuaishouCommentReplyItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / next_page_token / title
      Added value: +"Next Page Token"
    • addedOutput schema / title
      Added value: +"KuaishouVideoCommentRepliesResult"
  4. Changed2 schema fields changed
    • changedInput schema / properties / comment_id / description
      Previous value: -"一级评论 ID;从一级评论结果 items[].comment_id 复制,用于获取该评论下的回复;不要传回复项的 comment_id。"New value: +"一级评论 ID;用户已提供时直接使用,否则可从一级评论结果 items[].comment_id 复制;用于获取该评论下的回复;不要传回复项的 comment_id。"
    • changedInput schema / properties / photo_id / description
      Previous value: -"快手作品 photo_id;可从包含 photo_id 的快手作品结果中复用。"New value: +"快手作品 photo_id;用户已提供时直接使用,否则可从包含 photo_id 的快手作品结果中复用。"
  5. Changed2 schema fields changed
    • 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"
      -]New value: +[
      +  "items",
      +  "next_page_token",
      +  "points"
      +]
  6. Changed2 schema fields changed
    • changedOutput schema / properties / items / items / properties / author / properties / profile_url / description
      Previous value: -"快手用户主页链接;不是作品分享页链接;可作为后续需要快手用户主页 URL 的工具输入;如果是 live 主页且 user_id 为空,不要用于用户作品列表;不可用时为 null。"New value: +"快手用户主页链接;不是作品分享页链接;可作为后续需要快手用户主页 URL 的工具输入;查询用户作品列表时需确认同一用户结果包含非空 user_id;不可用时为 null。"
    • changedOutput schema / properties / items / items / properties / author / properties / user_id / description
      Previous value: -"快手用户 user_id;非空时可作为后续需要快手用户 user_id 的工具输入;部分 live 主页资料返回时 user_id 为空字符串,为空时不要作为后续 user_id 输入。"New value: +"快手用户 user_id;非空时可作为后续需要快手用户 user_id 的工具输入;为空字符串时不要作为后续 user_id 输入。"
  7. Changed3 schema fields changed
    • changedOutput schema / properties / items / items / properties / author / properties / profile_url / description
      Previous value: -"快手用户主页链接;不是作品分享页链接;可作为后续需要快手用户主页 URL 的工具输入;不可用时为 null。"New value: +"快手用户主页链接;不是作品分享页链接;可作为后续需要快手用户主页 URL 的工具输入;如果是 live 主页且 user_id 为空,不要用于用户作品列表;不可用时为 null。"
    • changedOutput schema / properties / items / items / properties / author / properties / user_id / description
      Previous value: -"快手用户 user_id;可作为后续需要快手用户 user_id 的工具输入。"New value: +"快手用户 user_id;非空时可作为后续需要快手用户 user_id 的工具输入;部分 live 主页资料返回时 user_id 为空字符串,为空时不要作为后续 user_id 输入。"
    • changedOutput schema / properties / items / items / properties / reply_to_user_id / description
      Previous value: -"被回复用户 user_id;可作为后续需要快手用户 user_id 的工具输入;不可用时为空字符串。"New value: +"被回复用户 user_id;非空时可作为后续需要快手用户 user_id 的工具输入;不可用时为空字符串,为空时不要作为后续 user_id 输入。"
  8. Changed2 schema fields changed
    • changedInput schema / properties / page_token / description
      Previous value: -"回复分页令牌。首次请求留空;继续翻页时传入上一页返回的 next_page_token。"New value: +"回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回;page_token 是不透明分页令牌;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。只能用于同一作品下同一一级评论的回复分页链路,不能跨能力、作品或评论复用。"
    • changedOutput schema / properties / next_page_token / description
      Previous value: -"下一页分页令牌;为空表示没有更多结果。"New value: +"下一页不透明分页令牌;为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路,不能跨能力、作品、用户、评论或搜索链路复用;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。"
  9. Changed3 schema fields changed
    • addedOutput schema / properties / items / items / properties / create_time
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "评论回复发布时间,秒级 Unix 时间戳;不可用时为 null。"
      +}
    • removedOutput schema / properties / items / items / properties / create_time_ms
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "integer"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "评论回复时间戳,毫秒;不可用时为 null。"
      -}
    • changedOutput schema / properties / items / items / required
      Previous value: -[
      -  "comment_id",
      -  "photo_id",
      -  "content",
      -  "create_time_ms",
      -  "like_count",
      -  "reply_to_user_name",
      -  "reply_to_user_id",
      -  "author"
      -]New value: +[
      +  "comment_id",
      +  "photo_id",
      +  "content",
      +  "create_time",
      +  "like_count",
      +  "reply_to_user_name",
      +  "reply_to_user_id",
      +  "author"
      +]
  10. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered and the description's added value is the input-correctness guard against supplying a reply-level comment_id. It says nothing about result shape, reply ordering, or pagination behavior beyond what the schema and output schema already carry.

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 purpose is front-loaded and every semicolon-delimited clause carries a distinct routing or guard instruction with no filler. It is dense, however, and reads as one long compound sentence rather than clearly separated usage rules.

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?

With an output schema present and full parameter documentation, the description only needs to cover selection and ID-sourcing, which it does. A reader still has to infer which concrete sibling tool supplies the missing comment_id, the one remaining completeness gap.

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 coverage is 100%, so all three parameters (including the strict opaque page_token rules) are already fully documented in the schema. The description reinforces that comment_id must be a top-level comment, but that constraint is already stated verbatim in the comment_id schema text, so it adds little beyond the structured field.

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 (get comment replies) scoped by photo_id plus a top-level comment_id, and the '一级评论' qualifier separates it from the sibling kuaishou_get_video_comments_by_photo_id. The closing warning against passing a reply item's comment_id further pins down what this tool is not for.

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 explicit conditional routing: use directly when the user supplied a complete valid ID pair, fall back to the top-level comment tool when a photo_id/link/share text exists but the comment_id is missing, and ask the user when video-locating info is absent. The only gap is that the alternative is referenced generically as '对应一级评论工具' rather than by its actual sibling name.

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