Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_list

List apps from Google Play top charts using collection, category, device, age, country, language, and count filters, with optional full app details.

Instructions

Retrieve apps from a Google Play top collection. Lists apps from a Google Play chart. collection is TOP_FREE, TOP_PAID, GROSSING, NEW_FREE or NEW_PAID, and category, device, age, num, country and lang narrow it. Set full_detail to get full app details instead of the compact card.

Input Schema

NameRequiredDescriptionDefault
ageNoFamily age range
numNoNumber of apps
langNoTwo-letter language code
deviceNoGoogle Play device tab: phone, tablet, tv, chromebook, watch, xr, car
countryNoTwo-letter country code
categoryNoCategory id
collectionNoCollection: TOP_FREE, TOP_PAID, GROSSING, NEW_FREE, NEW_PAID
full_detailNoResolve each app to full detail

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • addedInput schema / properties / collection / enum
      Added value: +[
+  "TOP_FREE",
+  "TOP_PAID",
+  "GROSSING",
+  "NEW_FREE",
+  "NEW_PAID"
+]
    • addedInput schema / properties / device / enum
      Added value: +[
+  "phone",
+  "tablet",
+  "tv",
+  "chromebook",
+  "watch",
+  "xr",
+  "car"
+]
  2. Changed2 schema fields changed
    • changedInput schema / properties / collection / description
      Previous value: -"Collection: TOP_FREE, TOP_PAID, GROSSING"New value: +"Collection: TOP_FREE, TOP_PAID, GROSSING, NEW_FREE, NEW_PAID"
    • addedInput schema / properties / device
      Added value: +{
+  "description": "Google Play device tab: phone, tablet, tv, chromebook, watch, xr, car",
+  "type": "string"
+}
  3. First observedv1.0.0

TDQS

B3.4/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 burden. It usefully discloses the compact-card vs full-detail output switch, but says nothing about pagination, rate limits, or defaults for the many optional filters.

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 and short at three sentences, with the key collection/param information up front. The first two sentences are near-duplicative ('Retrieve apps from a Google Play top collection' vs 'Lists apps from a Google Play chart'), a minor redundancy.

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

Completeness3/5

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

For an 8-param list tool with no annotations and no output schema, the description covers the selection and narrowing mechanics but omits return shape (beyond card vs detail), pagination, and defaults for optional filters, leaving meaningful gaps.

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 coverage is 100%, so the schema already documents all 8 parameters. The description restates the collection enum values and adds meaning only for full_detail ('full app details instead of the compact card'), which is modest added value over the schema.

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: retrieve/list apps from a Google Play top collection or chart. The 'top collection'/'chart' framing distinguishes it from the search-oriented sibling googleplay_search, though no sibling is named explicitly.

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?

It explains that collection selects the chart and the other params narrow it, and notes that full_detail switches output granularity. However there is no explicit when-to-use guidance versus googleplay_search, googleplay_similar, or the appstore_* counterparts, leaving selection to inference.

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