Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_reviews

Retrieve Google Play app reviews by app ID, sorted by newest, helpfulness, or rating, with pagination and fields like score, date, thumbs-up count, app version, and developer replies.

Instructions

Retrieve Google Play reviews. Returns Google Play reviews for an app by app_id. sort is newest (default), helpfulness or rating, and num is up to 1000 per request (default 100). Each review has its text, score, date, thumbs-up count, app version and any developer reply. Pass next_pagination_token back to continue.

Input Schema

NameRequiredDescriptionDefault
numNoNumber of reviews
langNoTwo-letter language code
sortNoSort: helpfulness, newest, rating
app_idYesGoogle Play app id
countryNoTwo-letter country code
paginateNoOnly fetch the requested page
next_pagination_tokenNoToken from a previous response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "helpfulness",
+  "newest",
+  "rating"
+]
  2. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses defaults (sort=newest, num=100), the 1000-per-request cap, the returned review fields (text, score, date, thumbs-up, app version, developer reply), and the pagination continuation mechanism. It omits only auth/rate-limit caveats.

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?

Four tight sentences, front-loaded with retrieval purpose, then configuration, then return shape, then pagination. Every sentence carries information an agent needs and none is redundant.

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?

With no output schema and no annotations, the description is complete enough: it explains the return fields, defaults, size cap, and how to page. It is slightly thin on the remaining optional filters (lang, country, paginate) but nothing essential for a correct call is 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 100%, so the baseline is 3, but the description adds value beyond the schema by supplying concrete defaults and a range ('num is up to 1000 per request (default 100)', 'sort is newest (default)') that the terse schema descriptions lack. lang, country, and paginate remain undocumented in the description.

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 (retrieve) and resource (Google Play reviews for an app scoped by `app_id`), which distinguishes it from aggregate tools like googleplay_ratings. No sibling is named explicitly, so it stops short of a 5, but the purpose is unambiguous.

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 only implied through the `app_id` scoping; there is no explicit when-to-use guidance or comparison to alternatives such as googleplay_ratings or appstore_reviews. The agent can infer it fetches review lists, but nothing routes it between siblings.

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