Crawlora MCP

googleplay_reviews

Read-only

Fetch Google Play reviews for an app package and storefront. Set paginate to true for one page or use the returned pagination token to continue; use googleplay_app for the app's details rather than its reviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "AppID": "<AppID>"
    },
    "name": "googleplay_reviews"
  }
}

Input Schema

Name	Required	Description
`Num`	No	Maximum number of reviews to return, default 100.
`Lang`	No	Two-letter language code, ISO-639, default en.
`Sort`	No	Review sort order, default newest. Allowed values: helpfulness, newest, rating.
`AppID`	Yes	Google Play package name (app ID), e.g. com.openai.chatgpt.
`Country`	No	Two-letter storefront country code, ISO-2, default us.
`Paginate`	No	When true, return only a single page; when false, auto-follow pages until num is reached. Default false.
`NextPaginationToken`	No	Pagination token from a previous response to fetch the next page of reviews.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the pagination continuation flow (single page vs token-follow), but that overlaps with what the schema already documents for Paginate and NextPaginationToken. Adds modest context beyond structured fields.

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?

Two tight sentences with zero waste. The core action and scope are front-loaded before the pagination and alternative-tool guidance.

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?

An output schema exists and annotations carry the safety profile, so return-value detail is not required in the description. The description covers purpose, sibling routing, and pagination adequately; only minor behavioral depth is missing.

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 all seven parameters (Num, Lang, Sort, AppID, Country, Paginate, NextPaginationToken) are already documented in the schema. The description only echoes app package, storefront, and pagination, adding no syntax or format detail beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Fetch') and resource ('Google Play reviews') scoped to 'an app package and storefront'. It explicitly distinguishes itself from the sibling googleplay_app, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool versus the alternative ('use googleplay_app for the app's details rather than its reviews') and how to control retrieval ('set paginate to true for one page or use the returned pagination token to continue'). No explicit when-not beyond that, but the alternative routing is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?