SocialDataX 快手 Kuaishou MCP

kuaishou_search_users

Read-only

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

Input Schema

TableJSON 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

TableJSON Schema

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

TDQS

A4.2/5.0

Behavior3/5

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

注解已包含readOnlyHint=true，描述未与此矛盾并补充了分页支持，但未提供更多行为细节（如返回结构、结果排序等）。由于注解已覆盖安全性，描述增加的内容有限，评分中规中矩。

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?

描述紧凑，两个句子传递了核心用途、排除条件和使用场景，信息密度高且无冗余。

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?

工具仅有2个参数且描述清晰，输出schema存在无需额外说明返回格式。描述覆盖了主要使用场景和翻页机制，但未提及返回字段或排序，在存在输出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?

输入schema覆盖100%，参数keyword和page_token均有详细描述。描述本身重复了schema中的约束（keyword不要传链接等），未提供超出schema的额外语义，因此评分基于schema覆盖率的基准3。

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?

使用明确的动词"搜索"和资源"快手用户"，并清晰说明了用途：按搜索词查找用户。同时明确区分了与已有用户主页链接或user_id时使用其他工具的差异，与兄弟工具区分明确。

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?

描述明确指出何时使用（按搜索词查找用户）和何时不使用（已有用户主页链接或user_id时改用对应用户资料或用户作品列表工具），并列出了keyword的禁止输入类型，提供了明确的替代路径。

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Every tool has a clear, distinct purpose. Pairs that differ by input method (profile URL vs user_id, photo_id vs URL) are clearly separated by input type, and no two tools appear to do the same thing. Search, user info, video details, comments, speech-to-text, and points balance are all unambiguous.

Naming Consistency4/5

The vast majority of tools follow a consistent `kuaishou_<verb>_<resource>[_by_<identifier>]` pattern (e.g., `kuaishou_get_user_info_by_user_id`). The only outlier is `socialdatax_get_points_balance`, which breaks the prefix convention but is still readable. Minor inconsistency lowers the score slightly.

Tool Count5/5

16 tools is well-scoped for a social media data access server. Each tool covers a distinct functional need—user info, videos, comments, speech-to-text, search, and account balance—without being excessive or sparse for the domain.

Completeness4/5

The tool surface covers the typical read-side workflows for Kuaishou: hot list, user profiles, user videos, video details, comments and replies, speech-to-text, and search. Minor gaps exist (e.g., no followers/following lists, no pagination on hot search), but these are not critical for the core purpose of retrieving public data.

Resources

Need Help?