youtube_channel_shorts
Read-onlyIdempotent
Channel shorts tab.
Bulk support: accepts ids for batched execution.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | ||
| ids | No | ||
| token | No | ||
| forUsername | No |
YouTube
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
TDQS
C2.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds bulk execution behavior, but provides no other behavioral context such as return format or authorization needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short with no redundant text, but it is more of a fragment than a structured tool description. It front-loads a noun phrase rather than a clear action statement.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has four parameters and no output schema, yet the description explains neither the return behavior nor the roles of token and forUsername. The bulk support note is helpful but leaves major gaps for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 0% schema description coverage, the description must compensate for undocumented parameters. It only clarifies 'ids' for batched execution, leaving id, token, and forUsername unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Channel shorts tab' identifies a resource but lacks a clear action verb, making it unclear whether the tool lists, retrieves, or performs another operation on shorts. The tool name and sibling context suggest retrieval, but the description itself is vague.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus alternatives like youtube_channel_videos or youtube_channel_shorts_post. The 'Bulk support' note is a parameter usage hint, not tool-selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.