Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_review

Fetches one app review by package name and review ID, including any developer reply, for read-only review inspection.

Instructions

Read one review by id, including the developer reply if any. Read-only.

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>",
      "reviewId": "<reviewId>"
    },
    "name": "get_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewIdYes
packageNameYesApplication id (package name), e.g. com.example.app
translationLanguageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does self-declare "Read-only" and discloses that the developer reply is included in the result, but says nothing about permissions/auth, what happens with an unknown or deleted review id, or how translationLanguage affects the returned content. For a tool with zero annotation coverage that is a notable gap.

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 short sentences, front-loaded with the action and scope, with the read-only and reply-inclusion facts stated plainly. Nothing is padded or redundant.

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?

With no output schema, the description does reasonably well by stating the result includes the review and any developer reply. However, it omits how translationLanguage changes the payload and what a caller gets for a nonexistent review, which matters for a single-record lookup.

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?

Only packageName is documented in the schema (33% coverage). The description links "by id" to reviewId but never describes its format (opaque id vs. numeric) or source, and translationLanguage is entirely unaddressed, even though it implies returned review text may be translated. Two of three parameters gain no meaning from 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?

"Read one review by id" names a specific verb and resource, and the singular scope plus "including the developer reply if any" tells an agent this is a single-record fetch rather than a list. It does not name the sibling read/write counterpart (reply_to_review), so the differentiation is only implicit through the singular scope.

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 implied by "Read one review by id" – an agent can infer it is for fetching a known review rather than browsing. There is no explicit when-to-use, when-not-to-use, or named alternative, and no note on whether a review must exist or what error surfaces for a bad id.

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