按用户 ID 获取好看视频用户发布视频列表，支持分页；持有用户主页链接时使用 haokan_get_user_posted_videos_by_profile_url。
| Name | Required | Description | Default |
|---|---|---|---|
| user_id | Yes | 好看视频用户 ID，可取用户搜索结果的 user_id，或视频详情、评论作者的 author.user_id；支持数字和字母数字标识，不要传空值。 | |
| page_token | No | 分页令牌，首次留空；续页原样传回上一页 next_page_token，且保持同一用户。 |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | 当前页用户发布视频，保持平台返回顺序。 | |
| points | Yes | 本次成功调用的积分消耗与账户积分余额。 | |
| next_page_token | Yes | 下一页分页令牌；为空表示没有下一页，续页需保持同一用户。 |
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 / cover_image_url / titleAdded value: +"Cover Image Url"Output schema / properties / items / items / properties / duration_seconds / titleAdded value: +"Duration Seconds"Output schema / properties / items / items / properties / publish_time_text / titleAdded value: +"Publish Time Text"Output schema / properties / items / items / properties / share_url / titleAdded value: +"Share Url"Output schema / properties / items / items / properties / title / titleAdded value: +"Title"Output schema / properties / items / items / properties / video_id / titleAdded value: +"Video Id"Output schema / properties / items / items / properties / view_count / titleAdded value: +"View Count"Output schema / properties / items / items / properties / view_count_text / titleAdded value: +"View Count Text"Output schema / properties / items / items / titleAdded value: +"HaokanUserPostedVideoItem"Output schema / properties / items / titleAdded value: +"Items"Output schema / properties / next_page_token / titleAdded value: +"Next Page Token"Output schema / titleAdded value: +"HaokanUserPostedVideosResult"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-data nature is known. The description adds that results are paginated, which is useful context beyond the annotations, but says nothing about ordering, rate limits, or empty-result behavior. With annotations covering the safety profile, a 3 is appropriate.
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?
One short sentence with the core action front-loaded, followed by the disambiguating routing clause. No filler or redundant restatement of the title.
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?
For a two-parameter read tool with full schema coverage, annotations, and an output schema, the description covers what is needed to call it correctly and when to prefer the sibling. Only the alternate ways of obtaining a user_id are left unstated.
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 already documents user_id sources, the allowed pattern, and the page_token continuation rule in more detail than the description. The mention of 分页 merely echoes the page_token parameter, so baseline 3 is correct.
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 precise verb and resource (retrieve the list of videos posted by a Haokan user, keyed by user ID) and explicitly names the sibling variant that takes a profile URL. An agent can select between the two without opening either schema.
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?
Gives a clear routing rule: use the profile_url sibling when holding a user homepage link, and this tool otherwise. It does not spell out the other common entry point (searching users first, or deriving user_id from a video/comment author), which the schema mentions but the description leaves implicit.
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.