Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

by com.52choujiang
OverviewDiscussionsAdmin

kuaishou_get_video_comment_replies_by_comment_id

Read-only

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

Input Schema

TableJSON 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

TableJSON 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
    • 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 的快手作品结果中复用。"
  2. 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"
+]
  3. 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 输入。"
  4. 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 输入。"
  5. 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 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论或搜索链路复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。"
  6. 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"
+]
  7. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, establishing safe read-only behavior and external dependencies. The description adds the constraint '不要传回复项的 comment_id' and the ID-completion workflow, but these are more about parameter semantics and usage rules than new behavioral context (e.g., rate limits, side effects). Thus, it adds minimal extra beyond annotations, warranting a 3.

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 a single, tightly-packed sentence (in Chinese) that front-loads the core purpose and then provides actionable rules. Every clause adds value, with no fluff or repetition. It is efficient and well-structured for an agent to parse quickly.

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?

Given the tool has an output schema, detailed parameter schema, and annotations (readOnly/openWorld), the description sufficiently covers the essential ID resolution workflow and cardinal rule about comment_id. It does not explicitly mention pagination behavior, but that is thoroughly documented in the schema for page_token. The only minor omission is lack of mention of error handling or invalid-ID scenarios, but those are often left to the system. Overall, it is complete for effective use.

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 description coverage is 100%, with detailed descriptions for all three parameters: photo_id derivation, comment_id (including the note about not using reply ids), and page_token (opaque, must reuse exactly). The description itself does not add new semantic detail beyond what the schema already states, only restating the comment_id constraint, so it earns the baseline score of 3.

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 clearly states the tool fetches comment replies given a photo_id and a first-level comment_id, and explicitly instructs not to pass reply-level comment_ids. This distinguishes it from sibling tools that retrieve first-level comments (kuaishou_get_video_comments_by_photo_id/by_url) and other video-focused tools, leaving no ambiguity about its specific function.

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 when-to-use instructions: use directly when a complete valid ID pair is provided, call the appropriate first-level comment tool when IDs are missing, request work location info from the user when needed, and never pass a reply comment_id. It names the alternative tools implicitly ('一级评论工具') and provides clear decision logic, which is more than typical guidance.

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

All SocialDataX 快手 Kuaishou MCP toolsInspect
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