Skip to main content
Glama
Sign In
google-play-developer-mcp

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reviews_list

Fetch app reviews from the last 7 days. Use a pagination token for more results and filter by language, translation language, or device.

Instructions

List reviews from the last 7 days. Use token from the previous page for pagination. Optional filters: language, translationLanguage, device.

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": {
      "packageName": "<packageName>"
    },
    "name": "reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNo
maxResultsNo
startIndexNo
packageNameYesAndroid application package name, e.g. com.example.app
translationLanguageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pagination behavior and optional filters but does not mention side effects, permissions, or what the response contains, leaving gaps in transparency.

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?

The description is concise (two sentences) and front-loads the purpose. However, the optional filters list is slightly inaccurate, which detracts from precision.

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?

Given the lack of output schema and annotations, the description covers the core purpose and pagination but misses details on startIndex, maxResults, and response structure, leaving some ambiguity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning for translationLanguage as a filter but incorrectly lists 'language' and 'device' which are not in the schema, while omitting descriptions for 'maxResults' and 'startIndex'. This mismatch reduces clarity.

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?

The description clearly states the action ('List reviews') and the time scope ('last 7 days'), distinguishing it from siblings like 'reviews_get' (single review) and 'reviews_reply'.

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 description provides basic guidance on pagination but does not explain when to use this tool versus alternatives like 'reviews_get' or 'reviews_reply', nor does it mention prerequisites or contexts where it should be avoided.

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