Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

googleplay_search

Search Google Play for apps matching a term with price, country, and language filters, returning up to 250 results or full app details.

Instructions

Search Google Play. Searches Google Play for apps matching the required term, up to num results (default 20, max 250). price is all (default), free or paid, and country and lang default to us and en. A strong exact match is placed first. An empty list means no apps matched.

Input 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

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does add real behavioral context: default and max result counts (20/250), the ordering guarantee that a strong exact match is placed first, and the meaning of an empty result list. It omits auth/rate-limit notes and says nothing about what full_detail changes in the response.

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?

Front-loaded with the core action and packed with useful defaults in a few sentences. Minor waste in the near-duplicate 'Search Google Play. Searches Google Play for apps...' opening.

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?

For a 6-parameter search with no annotations and no output schema, the description covers the key parameters, limits, ordering and empty-result semantics. The one notable gap is full_detail, whose effect on the returned data is left unexplained.

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 100%, so baseline is 3, but the description adds value beyond the schema by supplying the defaults and cap not documented there (num default 20 / max 250, price default all, country us, lang en). It does not explain the full_detail boolean.

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?

States a specific verb+resource: 'Search Google Play for apps matching the required `term`'. It is clearly distinguishable from entity-detail siblings like googleplay_app or googleplay_reviews, though it does not explicitly contrast with googleplay_suggest or googleplay_list.

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 (find apps by term), but the description never states when to choose this over googleplay_suggest, googleplay_list, or googleplay_categories, and offers no exclusions or preconditions.

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