按关键词搜索好看视频用户、账号或创作者，返回用户摘要并支持分页；不用于搜索视频。
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | 用户搜索词，例如账号名、创作者名称或品牌名；不要传视频链接、用户主页链接或分页令牌。 | |
| page_token | No | 分页令牌，首次请求留空；继续翻页时将上一页完整 next_page_token 原样传回，不得修改、截断或自行生成；只能用于相同工具和相同关键词。 |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | 当前页用户搜索结果。 | |
| points | Yes | 本次成功调用的积分消耗与账户积分余额。 | |
| next_page_token | Yes | 下一页不透明分页令牌；为空表示没有下一页。继续翻页时原样作为 page_token 传回，只能用于相同工具和相同关键词。 |
Changes observed during successful MCP inspections.
Output schema / properties / points / descriptionPrevious value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"Output schema / properties / points / properties / balance / descriptionPrevious value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"Output schema / properties / points / properties / balance / descriptionPrevious value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"Output schema / properties / points / properties / balance / minimumRemoved value: -0Output schema / properties / items / items / properties / avatar_url / titleAdded value: +"Avatar Url"Output schema / properties / items / items / properties / bio / titleAdded value: +"Bio"Output schema / properties / items / items / properties / follower_count / titleAdded value: +"Follower Count"Output schema / properties / items / items / properties / name / titleAdded value: +"Name"Output schema / properties / items / items / properties / posted_video_count / titleAdded value: +"Posted Video Count"Output schema / properties / items / items / properties / profile_url / titleAdded value: +"Profile Url"Output schema / properties / items / items / properties / user_id / titleAdded value: +"User Id"Output schema / properties / items / items / titleAdded value: +"HaokanSearchUserItem"Output schema / properties / items / titleAdded value: +"Items"Output schema / properties / next_page_token / titleAdded value: +"Next Page Token"Output schema / titleAdded value: +"HaokanUserSearchResult"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds the useful detail that results are user summaries and that the tool paginates. It does not discuss result caps, ordering, or rate limits, but with annotations plus an output schema the remaining burden is low.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence covering purpose, return shape, pagination, and the exclusion. No filler or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations covering the safety profile, an output schema covering return values, and full schema descriptions for both parameters, the description supplies everything essential for a search tool. Only the explicit sibling routing could be tightened.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and the schema itself already spells out keyword semantics and the strict page_token round-trip rules. The description adds nothing about parameter meaning beyond that, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (搜索) and resource (好看视频用户、账号或创作者), plus what is returned (用户摘要) and that pagination is supported. The closing clause "不用于搜索视频" explicitly distinguishes it from the sibling haokan_search_videos.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The negative clause "不用于搜索视频" gives a clear boundary against the most likely confusion, so an agent knows to route video queries elsewhere. It stops short of naming the alternative tool or explaining when to use this instead of the URL/user-id lookup siblings, which is a minor gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.