Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_suggest

Fetch up to 10 Google Play search suggestions for a term prefix; use two-letter country and language codes to target a storefront.

Instructions

Retrieve Google Play query suggestions. Returns up to 10 Google Play search suggestions for the term prefix in the path. country and lang take two-letter codes to pick the storefront and language. Each suggestion is a term.

Input Schema

NameRequiredDescriptionDefault
langNoTwo-letter language code
termYesSearch term prefix
countryNoTwo-letter country code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does add useful behavioral facts: the maximum result count ('up to 10') and the shape of each item ('a `term`'). However, it omits any statement about authentication requirements, rate limits, or what happens on an empty/invalid prefix, which for a zero-annotation tool is a gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, then result details, then parameter notes. Minimal waste, though 'Google Play query suggestions' and 'Google Play search suggestions' restate the same idea.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by describing the return ('up to 10' items, each a `term`). For a low-complexity 3-parameter read tool with no annotations, this covers what an agent needs to call it, with only auth/rate context missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description goes modestly beyond the schema by explaining the effect of the two code parameters ('to pick the storefront and language') and characterizing term as a prefix rather than a full query, which the schema wording does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource ('Retrieve Google Play query suggestions'), and by naming Google Play it is clearly distinguishable from the crowded sibling set of *_suggest tools (google_suggest, appstore_suggest, youtube_suggest). It further specifies the scope ('for the term prefix') and the result count.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by 'term prefix', which signals autocomplete/typeahead intent, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as googleplay_search for full search or googleplay_app for detail. The agent has to infer the intended context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools