Retrieve statistics, duration, and tags for up to 50 YouTube video IDs to analyze video performance and metadata.
Statistics, duration and tags for up to 50 video IDs.
| Name | Required | Description | Default |
|---|---|---|---|
| video_ids | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful context about the data fields returned (statistics, duration, tags) and the batch limit of 50, but does not cover other behavioral traits like rate limits or authentication.
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, front-loaded sentence that efficiently conveys the key information (what is returned and the batch limit) with no wasted words.
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 presence of an output schema and annotations, the description covers what the tool does and its batch limit. However, it lacks usage guidance for selecting this tool over siblings, leaving a gap for an agent to infer when to invoke it.
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 compensate for parameter semantics. It only repeats the parameter name ('video IDs') and a constraint already in the schema (max 50), without explaining the expected format (e.g., YouTube video ID strings) or any other details.
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 what data is returned (statistics, duration, tags) and the resource (video IDs), distinguishing it from sibling tools like channel overview or comment retrieval. No explicit verb, but the purpose is clear from context.
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?
No guidance on when to use this tool versus alternatives such as youtube_recent_uploads or youtube_search_videos. The description implies usage when you have video IDs, but no explicit conditions or exclusions are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.