Retrieve paginated watch history for your own Bilibili account; start with max and view_at at 0, then continue using the returned cursor values.
[账号] 分页读取本人观看历史；首次max/view_at=0，后续沿用响应cursor。
| Name | Required | Description | Default |
|---|---|---|---|
| ps | No | ||
| max | No | ||
| view_at | No | ||
| business | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the static hints in annotations (readOnlyHint: true), the description discloses the critical behavioral pattern of this tool: the pagination sequence. This guidance on using the response cursor is essential for successful tool invocation.
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?
The description is extremely concise, fitting its core function, scope, and the two most critical operational rules into a single, highly effective sentence.
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?
Given the complexity of pagination and the nature of a read-only history retrieval tool (which is confirmed safe by annotations), the description covers all necessary operational steps and behavioral constraints required for the AI to call it correctly.
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?
Since schema description coverage is 0%, the description is vital. It adds operational meaning to the pagination parameters (max/view_at) by explaining that they must be initialized to zero on the first request and replaced by a cursor on subsequent requests, which is not explicit in the schema definition.
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?
The description clearly defines the purpose: reading the user's own viewing history ('本人观看历史'). It is specific, utilizes the correct resource terminology, and distinguishes its function as a historical archive retrieval compared to other user data retrieval tools.
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?
It provides explicit usage guidelines regarding pagination. It mandates that the initial call must set max/view_at to 0, while subsequent calls must utilize the cursor from the response. This dictates the necessary operational workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.