YouTube Keyword Generator
get_v1_keyword_generator_youtubeYouTube Keyword Generator Group: Keyword Research. Billing per call: 1 Credits.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ||
| keyword | No |
get_v1_keyword_generator_youtubeYouTube Keyword Generator Group: Keyword Research. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| country | No | ||
| keyword | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses billing costs (1 credit per call), but does not mention other behavioral aspects like data returned, rate limits, or side effects. This is a partial disclosure.
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 brief and to the point, consisting of two sentences. It includes extra details (group, billing) without being verbose, and structure is clean.
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?
For a simple tool with two parameters, the description is sufficient for basic understanding. It lacks advanced context but is not incomplete for the tool's simplicity.
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 schema provides titles and examples for parameters (country, keyword), but the description adds no additional explanation about their meaning or format. Coverage is adequate but not enhanced.
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 tool's function as a YouTube keyword generator, and the title reinforces this. It distinguishes from sibling tools that target other platforms.
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?
While not explicit, the tool name and sibling list imply it is for YouTube keyword research. No explicit when-not-to-use guidance is given, but the context is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.