Retrieve up to 10 Google Play search suggestions for a given term, with optional country and language filters, to guide app discovery and keyword research.
Retrieve Google Play query suggestions. Returns up to 10 suggestions for a search term.
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Two-letter language code | |
| term | Yes | Search term prefix | |
| country | No | Two-letter country code |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It states 'Returns up to 10 suggestions', which adds some behavioral info, but lacks details on idempotency, rate limits, or results structure. It is minimally adequate.
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?
Two sentences, front-loaded with the action and result. No extraneous words. Every sentence earns its place.
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 simplicity of the tool (3 params, no output schema), the description is adequate. It covers the core behavior and constraint (up to 10). Slight lack of output format info, but acceptable.
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 coverage is 100%, so baseline is 3. The description adds context that the tool returns suggestions for a 'search term', but does not add meaning beyond the schema for 'country' and 'lang'. No value added beyond schema.
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 it retrieves Google Play query suggestions, distinguishing it from siblings like google_suggest (Google web) and googleplay_search (search results). The verb 'Retrieve' and resource 'Google Play query suggestions' is specific.
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 does not explicitly state when to use this tool versus alternatives such as googleplay_search or google_suggest. It only implies use when query suggestions are needed, but no when-not or alternative guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.