google_youtube_subscriptionsLists YouTube channels the user subscribes to for a chosen account. Use it to retrieve subscription lists and manage channel discovery.
List the channels the user subscribes to.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Account nickname to use. | |
| maxResults | No | Max results (default 50). |
Changes observed during successful MCP inspections.
v0.1.30Input schema / additionalPropertiesRemoved value: -falsev0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It states only the action (list) but does not indicate read-only nature, pagination, authentication requirements, or any side effects. An agent cannot infer safety or performance characteristics from this minimal text.
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 with no wasted words. It is concise and to the point, though it sacrifices informative detail. For a simple list tool, this level of brevity is acceptable, but it could include more context without becoming verbose.
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 that the tool has no output schema and no annotations, the description is the sole source of context. It explains what it does but omits when to use it, what happens with default values, and whether any side effects occur. For a read-only list operation, this may be sufficient, but in a large toolset it feels incomplete without usage guidance.
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?
The input schema covers both parameters (account and maxResults) with descriptions, achieving 100% coverage. The description adds no additional meaning beyond what the schema already provides, so the baseline of 3 applies. No extra context is given for how to format values or what constitutes a valid account.
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 the verb (List) and resource (channels the user subscribes to), which is distinct from other YouTube tools like list_playlists or my_videos. However, it doesn't explicitly differentiate from siblings beyond the resource name, and the title already conveys the same information. The purpose is clear but minimal.
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 provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites (e.g., account must be added), or exclusions. Given the large sibling set with several YouTube list tools, this is a significant gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.