List recent uploads from any YouTube channel by channel ID. Use maxResults to control up to 50 returned videos and check new content without subscribing.
List the most recent uploads of a specific channel (not required to be subscribed).
| Name | Required | Description | Default |
|---|---|---|---|
| channelId | Yes | The YouTube channel ID (UC...). | |
| maxResults | No | Max videos to return. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, and 'most recent' conveys ordering. However, it does not disclose any details about authentication, error behavior, or response structure, which is a moderate gap given the lack of annotations.
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, informative sentence that is front-loaded with the action and resource. No unnecessary words or repetition, making it highly concise and well-structured.
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?
The tool is a simple list operation with only two parameters, and the description covers its core purpose and key constraint (subscription not required). While there is no output schema to explain return values, the lack of that information is acceptable for a straightforward list tool. The description is sufficient, though slightly more detail about result contents would be ideal.
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?
The input schema has 100% coverage for both parameters (channelId and maxResults), so the schema already documents semantics fully. The description adds no additional parameter-level meaning beyond what the schema provides, which aligns with the baseline score of 3 for high schema coverage.
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 states the tool's function: listing the most recent uploads of a specific channel. It includes a scope qualifier ('not required to be subscribed') that distinguishes it from sibling tools like list_subscriptions and list_feed, which focus on subscriptions or the user's feed.
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 provides clear context for when to use the tool: for any channel's uploads, regardless of subscription status. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a full 'when/when-not' guideline.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.