youtube_list_recent_videosRetrieve recent videos from the configured YouTube channel. Specify max results and choose JSON or markdown output to get channel uploads.
List recent videos from the configured YouTube channel.
| Name | Required | Description | Default |
|---|---|---|---|
| max_results | No | ||
| response_format | No | json |
Changes observed during successful MCP inspections.
v0.1.6Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, etc. The description adds only that it accesses a configured channel, which is basic context. Lacks details on rate limits or result ordering.
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?
Single sentence is concise with no unnecessary words, but could benefit from a slightly more structured breakdown.
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 description is too sparse for a tool without output schema; it does not explain what 'recent' means, how results are ordered, or pagination behavior, leaving gaps for an agent.
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 coverage is 0% (no parameter descriptions), and the tool description does not mention or explain any parameters (max_results, response_format), leaving the agent without guidance beyond the schema structure.
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?
Description clearly states verb 'list' and resource 'recent videos from the configured YouTube channel', distinguishing it from siblings like youtube_upload_short or privacy_audit.
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?
Usage is implied by the simple purpose, but no explicit guidance on when to use vs. other tools (e.g., for searching) or when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.