Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_search

Search Google Play for apps by term and filter by price, country, language, or result count; returns structured app listings with optional full details.

Instructions

Search Google Play. Returns Google Play search results for a term.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoNumber of apps
langNoTwo-letter language code
termYesSearch term
priceNoPrice filter: all, free, paid
countryNoTwo-letter country code
full_detailNoResolve each app to full detail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / price / enum
      Added value: +[
+  "all",
+  "free",
+  "paid"
+]
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/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 only states that it returns search results, without disclosing any behavior such as result format, pagination, rate limits, or whether it requires network access. This is insufficient for a tool with no annotation coverage.

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?

Two short sentences with zero wasted words. The core action and return are front-loaded. It is appropriately sized for a simple search tool.

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?

While the schema covers parameters, the description doesn't explain what the returned 'search results' contain, nor does it mention any limitations or how the results can be used. Without an output schema, this is a notable gap. The agent gets no guidance on result structure or pagination.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all parameters including term, num, lang, price, country, and full_detail. The description adds no extra meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb ('Search') and resource ('Google Play'), and indicates it returns search results for a term. It is clear and distinct from the many sibling tools, though it doesn't explicitly mention 'apps' or differentiate from similar search tools like googleplay_suggest or appstore_search. Still, it is specific enough.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't mention any exclusions or prerequisites, nor does it compare to related tools such as googleplay_app or googleplay_suggest. The agent must infer its purpose from the name alone.

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