app-publish-mcp

google_list_reviews

List Google Play production app reviews with comments from the last 7 days, excluding ratings without comments and alpha/beta feedback. Use Play Console CSV export for older history.

Instructions

List production-app reviews with comments created or modified within the last 7 days. Ratings without comments and alpha/beta feedback are excluded. Requires Reply to reviews permission. pageToken pages only within that 7-day window; use Play Console CSV export for older history. An empty result alone does not indicate missing permission.

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": "google_list_reviews"
  }
}

Input Schema

Name	Required	Description
`pageToken`	No	Pagination token from a previous response (nextPageToken)
`maxResults`	No	Max reviews to return per page (API max is 100)
`packageName`	Yes	Android package name
`translationLanguage`	No	BCP-47 language code to translate review text into

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.7.0Oct 25, 2026

addedInput schema / properties / maxResults

Added value: +{
+  "description": "Max reviews to return per page (API max is 100)",
+  "type": "number"
+}

addedInput schema / properties / pageToken

Added value: +{
+  "description": "Pagination token from a previous response (nextPageToken)",
+  "type": "string"
+}

addedInput schema / properties / translationLanguage

Added value: +{
+  "description": "BCP-47 language code to translate review text into",
+  "type": "string"
+}

First observedv0.3.1Mar 19, 2026

TDQS

A4.3/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 discloses important behaviors: the 7-day window, exclusion of ratings without comments and alpha/beta feedback, the required 'Reply to reviews' permission, pagination confined to the window, and the caveat that an empty result does not indicate missing permission. It stops short of describing return fields or ordering, but covers the critical operational 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?

Five short sentences, front-loaded with the core scope and followed by critical caveats. Every sentence adds value with no repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with no annotations and no output schema, the description provides enough for correct invocation: scope, exclusions, permission requirement, pagination limitation, alternative for older data, and a false-negative warning. The schema covers parameter details; nothing essential 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 the schema already documents all four parameters. The description adds one useful nuance for pageToken ('pages only within that 7-day window') but says nothing about maxResults or translationLanguage beyond what the schema provides. Baseline 3 is appropriate.

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 states a specific verb and resource ('List production-app reviews') with clear scope: comments created or modified in the last 7 days, excluding ratings without comments and alpha/beta feedback. This readily distinguishes it from siblings like google_get_review (single review) and apple_list_reviews (different platform).

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?

It clearly establishes the context for use (recent production reviews with comments) and explicitly names an alternative for older history ('use Play Console CSV export'). It does not mention google_get_review or google_reply_to_review, but the guidance for this tool's appropriate scope is clear.

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

Deploy Server