Skip to main content
Glama

SocialDataX 快手 Kuaishou MCP

kuaishou_get_user_info_by_user_id

Read-only

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "kuaishou_get_user_info_by_user_id"
  }
}

Input Schema

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

Output 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
    • 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. Changed12 schema fields changed
    • addedOutput schema / properties / avatar_url / title
      Added value: +"Avatar Url"
    • addedOutput schema / properties / bio / title
      Added value: +"Bio"
    • addedOutput schema / properties / follower_count / title
      Added value: +"Follower Count"
    • addedOutput schema / properties / following_count / title
      Added value: +"Following Count"
    • addedOutput schema / properties / gender / title
      Added value: +"Gender"
    • addedOutput schema / properties / kuaishou_id / title
      Added value: +"Kuaishou Id"
    • addedOutput schema / properties / name / title
      Added value: +"Name"
    • addedOutput schema / properties / posted_content_count / title
      Added value: +"Posted Content Count"
    • addedOutput schema / properties / profile_url / title
      Added value: +"Profile Url"
    • addedOutput schema / properties / received_like_count / title
      Added value: +"Received Like Count"
    • addedOutput schema / properties / user_id / title
      Added value: +"User Id"
    • addedOutput schema / title
      Added value: +"KuaishouUserInfoData"
  4. 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"
      +]
  5. 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 的工具输入。"
  6. 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 输入。"
  7. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-dependency traits are covered. The description adds nothing further — no indication of what profile fields come back, latency, or failure behavior — and the schema parameter text carries the only non-obvious constraint.

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?

One short sentence, front-loaded with the key precondition. Nothing wasteful, though it is arguably too thin rather than too long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema, annotations, and a fully documented single parameter supply most of what an agent needs. The description itself does not help an agent choose between this and the profile-URL sibling, which is the main remaining 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?

With a single parameter at 100% schema coverage, the schema already explains reuse from prior user/author results and the empty-string exclusion. The description only restates 'non-empty user_id' without adding syntax or sourcing detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (获取用户资料) keyed on a Kuaishou user_id. This implicitly separates it from the sibling kuaishou_get_user_info_by_profile_url, though that alternative is never named.

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 offers no when-to-use or when-not guidance beyond the 'non-empty user_id' precondition, and does not point to kuaishou_get_user_info_by_profile_url for the URL case. The empty-string exclusion lives in the schema, not the description.

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