Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_list

Retrieve apps from any Google Play top collection and category, filtered by country, language, device, or age, and optionally resolve full app details.

Instructions

Retrieve apps from a Google Play top collection. Returns apps from a Google Play collection and category.

Input Schema

TableJSON 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

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, yet it only offers the read verb 'Retrieve.' It fails to disclose defaults (e.g., which collection is used if collection is omitted), result limits, whether collection/category are effectively required despite being optional in the schema, or how full_detail changes 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.

Conciseness3/5

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

The description is short and the verb is front-loaded, but the second sentence ('Returns apps from a Google Play collection and category') largely repeats the first, adding only 'category.' A single combined sentence would have been tighter with no loss of information.

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?

For a tool with 8 optional parameters, no annotations, and no output schema, the description is too thin. An agent cannot determine the default collection, expected result count, response shape, or when to prefer this over googleplay_search/googleplay_app. The schema covers parameter meaning but nothing about invocation behavior.

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 baseline is 3. The description adds a small cue that collection and category are the primary selection axes, but otherwise just echoes what the schema already documents, including the collection and device enums.

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 names a specific verb and resource — 'Retrieve apps from a Google Play top collection' — which is recognizable against siblings like googleplay_app, googleplay_search, and googleplay_reviews. However, it never explicitly differentiates itself from those siblings, and the second sentence largely restates the first, so it falls short of a 5.

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?

No guidance is given on when to use this tool versus googleplay_search, googleplay_app, googleplay_similar, or googleplay_ratings. There are no exclusions, prerequisites, or alternative routing conditions; the only hint is the word 'top collection,' which merely echoes the collection enum.

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