Retrieve recent videos from any YouTube channel using its URL, handle, or ID. Sort results by upload date or view count to locate relevant videos.
Get recent videos from a YouTube channel. Supports sorting by date or view count.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | YouTube channel URL, @handle, or channel ID | |
| order | No | Sort order (default: date) | |
| max_results | No | Number of videos to return (1-50, default: 25) |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The verb 'Get' conveys a read-only operation and the sorting behavior is mentioned, but no annotations exist to carry safety or side-effect information. The description does not address output shape, pagination, max_results behavior, authentication, or rate limits, leaving meaningful gaps.
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 concise sentences deliver the core purpose and key behavior with no filler. The description is front-loaded and every clause contributes meaningful information.
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 schema covers parameter semantics and the description gives a clear purpose, but the absence of annotations and output schema leaves return values, pagination, and selection versus sibling tools under-specified. It is adequate for simple invocation but not fully complete.
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%, so the schema already documents all three parameters with defaults and constraints. The description only restates the sort-by date or view count option, adding no information beyond what the schema provides.
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 the specific operation 'Get recent videos from a YouTube channel' and identifies the resource clearly. The sort options further define its scope, making it distinguishable from siblings like get_channel_info (channel metadata) and search_videos (broad video search).
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 implies the tool is for retrieving recent channel-level videos with sorting, but it does not explicitly say when to prefer it over alternatives like search_within_channel or search_videos. No exclusions or when-not-to-use guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.