SocialDataX 快手 Kuaishou MCP

kuaishou_search_users

Read-only

搜索快手用户。用户需要按搜索词查找用户时使用；keyword 只传搜索词，不要传作品链接，也不要传用户主页链接、photo_id 或 user_id；已有用户主页链接或 user_id 时使用对应用户资料或用户作品列表工具；支持 page_token 翻页。

Input Schema

Name	Required	Description	Default
`keyword`	Yes	搜索快手用户的搜索词，可传关键词或短语，例如人物名、账号名、品牌名或机构名；不要传作品链接，也不要传用户主页链接、photo_id、user_id 或 page_token。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。
`page_token`	No	用户搜索分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一用户搜索分页链路和同一关键词，不能跨能力、关键词或搜索链路复用。

Output Schema

Name	Required	Description
`items`	Yes	当前页用户结果列表。
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`next_page_token`	Yes	下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只能用于同一能力和同一分页链路，不能跨能力、作品、用户、评论或搜索链路复用；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed10 schema fields changedNov 3, 2026
- addedOutput schema / properties / items / items / properties / avatar_url / title
```
Added value: +"Avatar Url"
```
- addedOutput schema / properties / items / items / properties / bio / title
```
Added value: +"Bio"
```
- addedOutput schema / properties / items / items / properties / name / title
```
Added value: +"Name"
```
- addedOutput schema / properties / items / items / properties / profile_url / title
```
Added value: +"Profile Url"
```
- addedOutput schema / properties / items / items / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / properties / items / items / properties / verified / title
```
Added value: +"Verified"
```
- addedOutput schema / properties / items / items / title
```
Added value: +"KuaishouUserSearchItemData"
```
- addedOutput schema / properties / items / title
```
Added value: +"Items"
```
- addedOutput schema / properties / next_page_token / title
```
Added value: +"Next Page Token"
```
- addedOutput schema / title
```
Added value: +"KuaishouUserSearchResult"
```

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / keyword / description

Previous value: -"搜索快手用户的自然语言关键词。传人物名、账号名、品牌名或机构名等关键词；不要传作品链接，不要传用户主页链接、photo_id、user_id 或 page_token 作为 keyword。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。"New value: +"搜索快手用户的搜索词，可传关键词或短语，例如人物名、账号名、品牌名或机构名；不要传作品链接，也不要传用户主页链接、photo_id、user_id 或 page_token。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。"

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: -[
-  "items",
-  "next_page_token"
-]New value: +[
+  "items",
+  "next_page_token",
+  "points"
+]

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / keyword / description

Previous value: -"搜索快手用户的自然语言关键词。传人物名、账号名、品牌名或机构名等关键词；不要传作品链接，不要传用户主页链接、photo_id 或 user_id。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。"New value: +"搜索快手用户的自然语言关键词。传人物名、账号名、品牌名或机构名等关键词；不要传作品链接，不要传用户主页链接、photo_id、user_id 或 page_token 作为 keyword。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。"

Changed2 schema fields changedJul 8, 2026

changedOutput schema / properties / items / items / properties / profile_url / description

Previous value: -"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；如果是 live 主页且 user_id 为空，不要用于用户作品列表；不可用时为 null。"New value: +"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；查询用户作品列表时需确认同一用户结果包含非空 user_id；不可用时为 null。"

changedOutput schema / properties / items / items / properties / user_id / description

Previous value: -"快手用户 user_id；非空时可作为后续需要快手用户 user_id 的工具输入；部分 live 主页资料返回时 user_id 为空字符串，为空时不要作为后续 user_id 输入。"New value: +"快手用户 user_id；非空时可作为后续需要快手用户 user_id 的工具输入；为空字符串时不要作为后续 user_id 输入。"

Changed3 schema fields changedJul 7, 2026

changedInput schema / properties / keyword / description

Previous value: -"搜索快手用户的自然语言关键词。传人物名、账号名、品牌名或机构名等关键词；不要传作品链接，不要传用户主页链接、photo_id 或 user_id。已有用户主页链接或 user_id 时改用需要快手用户主页 URL/user_id 的入口。"New value: +"搜索快手用户的自然语言关键词。传人物名、账号名、品牌名或机构名等关键词；不要传作品链接，不要传用户主页链接、photo_id 或 user_id。已有用户主页链接或非空 user_id 时改用需要快手用户主页 URL/user_id 的入口。"

changedOutput schema / properties / items / items / properties / profile_url / description

Previous value: -"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；不可用时为 null。"New value: +"快手用户主页链接；不是作品分享页链接；可作为后续需要快手用户主页 URL 的工具输入；如果是 live 主页且 user_id 为空，不要用于用户作品列表；不可用时为 null。"

changedOutput schema / properties / items / items / properties / user_id / description

Previous value: -"快手用户 user_id；可作为后续需要快手用户 user_id 的工具输入。"New value: +"快手用户 user_id；非空时可作为后续需要快手用户 user_id 的工具输入；部分 live 主页资料返回时 user_id 为空字符串，为空时不要作为后续 user_id 输入。"

AddedJul 1, 2026

TDQS

A4.3/5.0

Behavior3/5

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

The annotations already establish a non-mutating, open-world read operation. The description adds pagination support and routing constraints, but provides little further operational context such as search limitations or result freshness; detailed pagination behavior is carried by the schema.

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 compact and front-loads the action and use case before presenting exclusions, alternatives, and pagination. Its semicolon-separated clauses are dense, but each supports correct selection or invocation without filler.

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 two-parameter read-only search with fully described inputs and an output schema, the description supplies the necessary scope, routing guidance, and pagination context. Together with the structured fields, it gives the agent enough information to select and invoke the tool correctly.

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%, with extensive documentation for both keyword and page_token, including first-page use and opaque-token handling. The description mostly repeats the keyword exclusions and briefly mentions pagination, so it adds little parameter meaning beyond 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 opening “搜索快手用户” states a specific verb and resource, while “按搜索词查找用户” defines the search-by-keyword scope. The exclusions for video links, profile links, and IDs distinguish it from video search and direct user-information or posted-video siblings.

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?

It explicitly says when to use the tool, which inputs not to pass, and when to switch to user-profile or user-video-list tools instead. Although alternatives are described by category rather than exact tool name, those categories map directly to the supplied siblings.

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?