youtube_home_feed
Read-onlyIdempotent
YouTube home feed (anonymous, geo/lang aware).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| geo | No | ||
| lang | No | ||
| token | No |
YouTube
Schema Changelog
Changes observed during successful MCP inspections.
- First observed
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds context about anonymity and geo/lang awareness, but does not disclose return format, pagination, or any additional behavioral traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence with no fluff, front-loaded with the core purpose. Every word adds value, 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.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 3 optional parameters and no schema details, the description fails to explain the token parameter or describe the output shape. It is minimally complete for a simple read-only tool but leaves significant gaps for an agent to infer usage.
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?
Schema has 3 parameters (geo, lang, token) with 0% coverage. The description implies geo/lang usage but does not explain their format or any meaning, and the token parameter is completely undocumented, leaving it ambiguous for the agent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool does: returns the YouTube home feed with anonymous access and geo/lang awareness. It distinguishes itself from siblings like youtube_trending or youtube_channel_home, though it doesn't explicitly name alternatives.
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 on when to use this tool vs alternatives. It does not mention exclusions, prerequisites, or specific scenarios where this tool is preferred over others like youtube_search or youtube_trending.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.