Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

by com.52choujiang
OverviewDiscussionsAdmin

kuaishou_get_user_info_by_user_id

Read-only

根据快手用户非空 user_id 获取用户资料。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes快手用户非空 user_id；可从包含非空 user_id 的快手用户或作者结果中复用；如果上一步结果里的 user_id 为空字符串，不要使用 user_id 入口。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYes用户简介；不可用时为空字符串。
nameYes用户名称。
genderYes用户性别。
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
user_idYes快手用户非空 user_id；可作为后续需要快手用户 user_id 的工具输入。
avatar_urlYes用户头像链接；不可用时为 null。
kuaishou_idYes快手号；不可用时为 null。
profile_urlYes快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；查询用户作品列表时需确认同一用户结果包含非空 user_id；不可用时为 null。
follower_countYes粉丝数；不可用时为 null。
following_countYes关注数；不可用时为 null。
received_like_countYes获赞数；表示用户内容累计收到的点赞数；不可用时为 null。
posted_content_countYes公开作品数；不可用时为 null。

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: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "kuaishou_id",
-  "bio",
-  "gender",
-  "follower_count",
-  "following_count",
-  "received_like_count",
-  "posted_content_count"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "kuaishou_id",
+  "bio",
+  "gender",
+  "follower_count",
+  "following_count",
+  "received_like_count",
+  "posted_content_count",
+  "points"
+]
  2. Changed2 schema fields changed
    • changedOutput schema / properties / profile_url / description
      Previous value: -"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；如果是 live 主页且 user_id 为空，不要用于用户作品列表；不可用时为 null。"New value: +"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；查询用户作品列表时需确认同一用户结果包含非空 user_id；不可用时为 null。"
    • changedOutput schema / properties / user_id / description
      Previous value: -"快手用户 user_id；非空时可作为后续需要快手用户 user_id 的工具输入；部分 live 主页资料返回时 user_id 为空字符串，为空时不要作为后续 user_id 输入。"New value: +"快手用户非空 user_id；可作为后续需要快手用户 user_id 的工具输入。"
  3. Changed3 schema fields changed
    • changedInput schema / properties / user_id / description
      Previous value: -"快手用户 user_id；可从包含 user_id 的快手用户或作者结果中复用。"New value: +"快手用户非空 user_id；可从包含非空 user_id 的快手用户或作者结果中复用；如果上一步结果里的 user_id 为空字符串，不要使用 user_id 入口。"
    • changedOutput schema / properties / profile_url / description
      Previous value: -"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；不可用时为 null。"New value: +"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；如果是 live 主页且 user_id 为空，不要用于用户作品列表；不可用时为 null。"
    • changedOutput schema / properties / user_id / description
      Previous value: -"快手用户 user_id；可作为后续需要快手用户 user_id 的工具输入。"New value: +"快手用户 user_id；非空时可作为后续需要快手用户 user_id 的工具输入；部分 live 主页资料返回时 user_id 为空字符串，为空时不要作为后续 user_id 输入。"
  4. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare this as a read-only operation (readOnlyHint=true). The description adds the non-empty user_id constraint, which is useful but not a deep behavioral disclosure. There is no mention of error behavior, result shape, or access requirements beyond the annotations, so it meets baseline but does not exceed it.

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, concise sentence that immediately states the tool's purpose. It is front-loaded and contains no filler, making it easy for an agent to parse quickly.

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?

For a simple read-only lookup tool with one parameter, an output schema, and clear annotations, the description is sufficiently complete. The schema covers input constraints, and the annotation covers safety, so the description only needs to state the primary function, which it does.

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 the parameter is fully documented in the schema. The tool description adds no additional parameter semantics beyond what the schema already provides. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 user profile data using a non-empty Kuaishou user_id. It specifies the resource ('user profile') and the identifier type ('user_id'), which distinguishes it from sibling tools that use profile URLs or other access methods.

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 and the schema together clarify when to use this tool: when a non-empty user_id is available, potentially from previous results. The schema explicitly warns against using it when user_id is an empty string. However, no explicit mention of alternative tools (like the profile URL variant) is provided, so it lacks explicit exclusions.

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