Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

by com.52choujiang
OverviewDiscussionsAdmin

kuaishou_get_video_comments_by_photo_id

Read-only

根据快手作品 photo_id 获取一级评论列表。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
photo_idYes快手作品 photo_id；用户已提供时直接使用，否则可从包含 photo_id 的快手作品结果中复用。
page_tokenNo分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 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 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论或搜索链路复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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",
-  "comment_count"
-]New value: +[
+  "items",
+  "next_page_token",
+  "comment_count",
+  "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. Changed2 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 输入。"
  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",
-  "has_replies",
-  "author"
-]New value: +[
+  "comment_id",
+  "photo_id",
+  "content",
+  "create_time",
+  "like_count",
+  "has_replies",
+  "author"
+]
  7. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint: true, which is fully consistent with the description's '获取' (get). The description does not contradict annotations and adds minimal context beyond them. It does not describe any side effects, rate limits, or special behavior beyond what annotations imply. With annotations covering the safety profile, a score of 3 is appropriate—it meets the minimum but does not enrich the behavioral picture further.

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, front-loaded sentence in Chinese that conveys the core purpose without any wasted words. It is appropriately sized for a tool with simple parameters and a clear role, and the key information (what it gets and how) is placed first. This is exemplary conciseness.

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 that an output schema exists and the parameter schema covers pagination details, the description's brevity is acceptable. It captures the essential function and distinguishes the scope (first-level comments). However, it could have explicitly mentioned that it returns a paginated list or that page_token handles continuation, but that information resides in the schema. Overall, it is sufficiently complete for an agent to call correctly, with only minor additional context possible.

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%, so both parameters (photo_id and page_token) are already documented in detail in the schema. The tool description adds no additional parameter meaning beyond the schema. Since the schema handles the parameter semantics adequately, the baseline of 3 applies. The description itself does not mention parameters, but the schema does the heavy lifting, so no penalty.

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 action (获取 = get), the resource (快手作品 photo_id 的一级评论列表 = first-level comment list for a Kuaishou work by photo_id), and the specific parameter (photo_id). It distinguishes from siblings like kuaishou_get_video_comments_by_url (by URL) and kuaishou_get_video_comment_replies_by_comment_id (replies) by explicitly mentioning '一级评论' (first-level). This is a specific verb+resource statement that leaves no ambiguity about the tool's purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any explicit guidance on when to use this tool versus alternatives like kuaishou_get_video_comments_by_url or kuaishou_get_video_comment_replies_by_comment_id. It only states what it does, leaving the agent to infer selection criteria from the parameter (photo_id) and the tool name. There is no mention of exclusions, prerequisites, or alternative conditions, which is a significant gap for an agent deciding among multiple comment-related tools.

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