Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

by com.52choujiang
OverviewDiscussionsAdmin

kuaishou_get_video_comments_by_url

Read-only

根据快手作品链接、短链接或分享文案获取一级评论列表；不要传用户主页链接；查评论时保留原始 URL/文案使用 URL 入口。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes快手作品页链接、短链接或分享文案；不要传用户主页链接。查评论时如果手里有原始作品链接、短链接或分享文案，保留原始 URL/文案并直接使用 URL 入口。
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. 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"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"快手作品页链接、短链接或分享文案；不要传用户主页链接。如果上一步结果已返回 photo_id，可直接使用 photo_id 入口。"New value: +"快手作品页链接、短链接或分享文案；不要传用户主页链接。查评论时如果手里有原始作品链接、短链接或分享文案，保留原始 URL/文案并直接使用 URL 入口。"
  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.9/5.0
Behavior3/5

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

Annotations already include readOnlyHint=true, so the read-only nature is covered. The description adds that it returns first-level comments and warns against using user profile links, which is useful context beyond annotations. However, it does not disclose pagination behavior, rate limits, or error handling, leaving gaps that the schema partially fills.

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 description is concise, with a clear main action followed by a constraint and a usage tip. It is front-loaded and each clause serves a purpose, though it is slightly redundant with the schema's url description, keeping it from being perfectly tight.

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, read-only annotations, and well-documented parameters, the description is largely complete for its complexity. It clarifies the input form and scope (first-level comments) but does not elaborate on pagination flow or response structure, which are reasonably covered by the schema and output schema.

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?

The input schema already covers both parameters with detailed descriptions (url and page_token), achieving 100% coverage. The description's parameter-related content (preserve original URL, exclude user homepage) largely duplicates what the schema says, so it adds minimal new semantic value beyond the structured fields.

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's function: fetching first-level comments based on Kuaishou video links, short links, or shared text. It also provides a specific exclusion (user homepage links) and distinguishes from the photo_id-based sibling by emphasizing URL entry, making the purpose unambiguous.

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?

The description gives explicit usage guidance: do not pass user homepage links, and when querying comments keep the original URL/text and use the URL entry. It does not explicitly name alternative tools (e.g., the photo_id variant), but the context and input constraints convey when this tool is appropriate.

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