Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

googleplay_reviews

Fetch Google Play app reviews by app ID, with filters for country, language, sort order, and pagination; set paginate=true to retrieve only the requested page.

Instructions

Retrieve Google Play reviews. Returns one or more pages of app reviews. Set paginate=true to fetch only the requested page.

Input Schema

TableJSON 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

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It reveals that pagination exists but leaves the default behavior ambiguous — what happens when paginate is not set, and how 'the requested page' is identified (presumably via next_pagination_token) is never explained.

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?

Two sentences with the purpose front-loaded and no filler. The pagination sentence earns its place, though it could be worded more clearly.

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 7-parameter tool with no annotations and no output schema, the description is thin. It omits default paging behavior and the relationship between paginate and next_pagination_token, leaving an agent unable to reliably request a specific page or know what a default call returns.

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 reinforces the paginate parameter but adds no meaning beyond the schema's 'Only fetch the requested page'; defaults for num, lang, country, and sort remain undocumented in both places.

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 opens with a specific verb and resource ('Retrieve Google Play reviews') and clarifies the return shape ('Returns one or more pages of app reviews'). It clearly identifies the tool's domain, though it does not explicitly distinguish it from sibling review tools like appstore_reviews or googleplay_ratings.

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?

The only usage guidance is the pagination instruction ('Set paginate=true to fetch only the requested page'), which is a parameter-level hint rather than when-to-use guidance. No mention of when to prefer this over alternatives such as googleplay_ratings (aggregate ratings) or appstore_reviews (iOS reviews).

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