按视频 ID读取好看视频一级评论，支持分页；附带的回复仅为预览。另一种输入使用 haokan_get_video_comments_by_url。
| Name | Required | Description | Default |
|---|---|---|---|
| video_id | Yes | 好看视频数字 ID，以字符串传入，例如 6148991337208256393；可从视频搜索结果的 video_id 获取。 | |
| page_token | No | 分页令牌，首次留空；续页原样传回 next_page_token，保持同一视频。 |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | 当前页一级评论，保持平台顺序。 | |
| points | Yes | 本次成功调用的积分消耗与账户积分余额。 | |
| comment_count | 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 / comment_count / titleAdded value: +"Comment Count"Output schema / properties / items / items / properties / author / properties / avatar_url / titleAdded value: +"Avatar Url"Output schema / properties / items / items / properties / author / properties / name / titleAdded value: +"Name"Output schema / properties / items / items / properties / author / properties / profile_url / titleAdded value: +"Profile Url"Output schema / properties / items / items / properties / author / properties / user_id / titleAdded value: +"User Id"Output schema / properties / items / items / properties / author / titleAdded value: +"HaokanCommentAuthor"Output schema / properties / items / items / properties / comment_id / titleAdded value: +"Comment Id"Output schema / properties / items / items / properties / content / titleAdded value: +"Content"Output schema / properties / items / items / properties / create_time / titleAdded value: +"Create Time"Output schema / properties / items / items / properties / image_urls / titleAdded value: +"Image Urls"Output schema / properties / items / items / properties / like_count / titleAdded value: +"Like Count"Output schema / properties / items / items / properties / replies / items / properties / author / properties / avatar_url / titleAdded value: +"Avatar Url"Output schema / properties / items / items / properties / replies / items / properties / author / properties / name / titleAdded value: +"Name"Output schema / properties / items / items / properties / replies / items / properties / author / properties / profile_url / titleAdded value: +"Profile Url"Output schema / properties / items / items / properties / replies / items / properties / author / properties / user_id / titleAdded value: +"User Id"Output schema / properties / items / items / properties / replies / items / properties / author / titleAdded value: +"HaokanCommentAuthor"Output schema / properties / items / items / properties / replies / items / properties / comment_id / titleAdded value: +"Comment Id"Output schema / properties / items / items / properties / replies / items / properties / content / titleAdded value: +"Content"Output schema / properties / items / items / properties / replies / items / properties / create_time / titleAdded value: +"Create Time"Output schema / properties / items / items / properties / replies / items / properties / image_urls / titleAdded value: +"Image Urls"Output schema / properties / items / items / properties / replies / items / properties / like_count / titleAdded value: +"Like Count"Output schema / properties / items / items / properties / replies / items / titleAdded value: +"HaokanCommentReply"Output schema / properties / items / items / properties / replies / titleAdded value: +"Replies"Output schema / properties / items / items / properties / reply_count / titleAdded value: +"Reply Count"Output schema / properties / items / items / properties / video_id / titleAdded value: +"Video Id"Output schema / properties / items / items / titleAdded value: +"HaokanCommentItem"Output schema / properties / items / titleAdded value: +"Items"Output schema / properties / next_page_token / titleAdded value: +"Next Page Token"Output schema / titleAdded value: +"HaokanVideoCommentsResult"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint and openWorldHint; the description adds substantive behavior beyond that: results are paginated, only first-level comments are returned, and any included replies are a preview rather than the full reply set. It does not discuss rate limits or ordering, but the key expectation-setting (scope of returned comments) is present.
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?
Two short clauses: the capability and scope first, then the alternative-input pointer. Every clause carries information — no filler, no repetition 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 simple two-parameter read tool with full schema coverage, read-only annotations, and an output schema, the description covers the essentials: what is returned, pagination, and the URL-based alternative. The only minor omission is not naming the replies tool needed to expand the previewed replies.
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 both parameters are documented in-schema with format, pattern, and pagination-token semantics. The description adds nothing about parameter handling beyond restating 'by video ID' and 'supports pagination', so the baseline of 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+resource: reading top-level (一级) comments of a Haokan video by numeric video ID, with pagination. It also explicitly names the sibling haokan_get_video_comments_by_url and the differentiator (URL input vs video ID), so an agent can pick between them without inspecting schemas.
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 this tool when you have a video ID, and use haokan_get_video_comments_by_url for the URL-based input. It also signals that bundled replies are preview-only, hinting at the replies tools, though it never names haokan_get_comment_replies_by_video_id as the follow-up for full replies.
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.