SocialDataX 快手 Kuaishou MCP

kuaishou_get_user_info_by_profile_url

Read-only

根据快手用户主页链接、短链接或分享文案获取用户资料；支持 live 主页和 fw/user 用户主页分享链接，成功时会返回可复用的非空 user_id；不要传作品链接。如果上一步结果已返回非空 user_id，可直接使用 user_id 入口。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`profile_url`	Yes	快手用户主页链接、短链接或分享文案；不要传作品链接。支持 live 主页或 fw/user 形式的用户主页分享链接；成功时会返回可复用的非空 user_id。如果上一步结果已返回非空 user_id，可直接使用 user_id 入口。

Output Schema

TableJSON Schema

Name	Required	Description
`bio`	Yes	用户简介；不可用时为空字符串。
`name`	Yes	用户名称。
`gender`	Yes	用户性别。
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`user_id`	Yes	快手用户非空 user_id；可作为后续需要快手用户 user_id 的工具输入。
`avatar_url`	Yes	用户头像链接；不可用时为 null。
`kuaishou_id`	Yes	快手号；不可用时为 null。
`profile_url`	Yes	快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；查询用户作品列表时需确认同一用户结果包含非空 user_id；不可用时为 null。
`follower_count`	Yes	粉丝数；不可用时为 null。
`following_count`	Yes	关注数；不可用时为 null。
`received_like_count`	Yes	获赞数；表示用户内容累计收到的点赞数；不可用时为 null。
`posted_content_count`	Yes	公开作品数；不可用时为 null。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026

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"
+]

Changed3 schema fields changedJul 8, 2026

changedInput schema / properties / profile_url / description

Previous value: -"快手用户主页链接、短链接或分享文案；不要传作品链接。支持 live 主页或 fw/user 形式的用户主页分享链接；这类资料返回的 user_id 可能为空，为空时不要作为后续 user_id 输入。如果上一步结果已返回非空 user_id，可直接使用 user_id 入口。"New value: +"快手用户主页链接、短链接或分享文案；不要传作品链接。支持 live 主页或 fw/user 形式的用户主页分享链接；成功时会返回可复用的非空 user_id。如果上一步结果已返回非空 user_id，可直接使用 user_id 入口。"

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 的工具输入。"

Changed3 schema fields changedJul 7, 2026

changedInput schema / properties / profile_url / description

Previous value: -"快手用户主页链接、短链接或分享文案；不要传作品链接。如果上一步结果已返回 user_id，可直接使用 user_id 入口。"New value: +"快手用户主页链接、短链接或分享文案；不要传作品链接。支持 live 主页或 fw/user 形式的用户主页分享链接；这类资料返回的 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 输入。"

First observedJun 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses key behaviors: supports live and fw/user share links, returns a reusable non-empty user_id on success, and rejects work links. Annotations already cover read-only safety (readOnlyHint: true), so the description adds value by detailing the return value guarantee and input constraints. No contradiction with annotations.

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, well-structured sentence that front-loads the purpose and flows logically through input types, success behavior, exclusions, and usage guidance. Every clause earns its place; no filler or redundancy.

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 one-parameter read-only tool with an output schema, the description covers all necessary context: input formats, supported link types, prohibited input, output behavior (non-empty user_id), and when to use an alternative. It is complete for the tool's complexity.

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 schema already provides 100% coverage for the single parameter profile_url, with the same detailed description of accepted formats and constraints. The tool description adds no new semantic information beyond what's in the schema, so the baseline 3 applies. It simply reinforces the schema.

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: '根据快手用户主页链接、短链接或分享文案获取用户资料' (get user profile from profile URL). It specifies the exact input type (profile URL, short link, share text) and distinguishes from sibling tools by mentioning the user_id entry and excluding work links. This is a specific verb+resource with clear differentiation.

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 explicitly says '如果上一步结果已返回非空 user_id，可直接使用 user_id 入口', advising to use the user_id entry (sibling tool) when a non-empty user_id already exists. It also says '不要传作品链接' (don't pass work links), providing a clear exclusion. This is explicit when-to-use and when-not-to-use guidance with a stated alternative.

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 tools Inspect

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

Need Help?