Retrieve an uploader's collection list with IDs, names, and video counts. Use these details to fetch videos from a specific collection via get_collection_videos.
UP 主的合集/系列列表（课程大多以合集组织）。返回 id/name/total，配合 get_collection_videos 用。
| Name | Required | Description | Default |
|---|---|---|---|
| mid | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It does disclose the output shape (id/name/total) and provides context that courses are organized as collections, but it omits pagination, ordering, or rate-limit behavior, so it is only partially transparent.
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 a single concise sentence that packs purpose, return fields, and a pointer to the companion tool without any filler. Every element is load-bearing.
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 one-parameter listing tool with no output schema, the description provides the core call path and return contract, and orients the agent to the relevant sibling. The main gap is the lack of pagination or sorting behavior, which an agent might still need to discover.
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 0%, so the description must clarify the mid parameter. The phrase 'UP主的合集' implies mid identifies the uploader, but this is never explicitly stated nor are any constraints or examples given. The schema's bare 'mid' title provides minimal help.
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 states a specific verb and resource: listing the uploader's collections/series, with an added detail that most courses are organized as collections. It also names the return fields (id/name/total), which clearly distinguishes it from sibling tools like get_collection_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 description explicitly says to use it together with get_collection_videos, giving an agent a clear next step and establishing this tool as the collection-level listing entry point. It does not spell out when-not-to-use it, but for a simple list tool this is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.