Google Play MCP

reporting_request

Makes raw GET or POST requests to Google Play Developer Reporting API endpoints not covered by other tools, such as searching error reports by package name.

Instructions

Raw call to the OPTIONAL Play Developer Reporting API (playdeveloperreporting.googleapis.com, v1beta1) for anything not covered above, e.g. '/apps/{packageName}/errorReports:search'. path is relative to /v1beta1. The Reporting API is read-only, so this is allowed in read-only mode.

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": {
      "method": "<method>",
      "path": "<path>"
    },
    "name": "reporting_request"
  }
}

Input Schema

Name	Required	Description
`body`	No	JSON request body (for POST ...:query)
`path`	Yes
`query`	No	Query params as a flat object
`method`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.1/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 load and does disclose that the Reporting API is read-only and therefore safe in read-only mode — useful safety context an agent could not otherwise infer. It does not mention authentication, error behavior, or response shape, so it stops short of full disclosure.

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?

Three short sentences, front-loaded with what the tool is and the path-base constraint; every clause carries information and nothing is repeated from the schema.

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?

For a 4-parameter passthrough with no annotations and no output schema, the description supplies the essentials: the API surface, the path base, an example of the target form, and the read-only safety profile. Missing only error/return behavior, which matters less given this is a deliberate raw escape hatch.

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

Parameters4/5

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

At 50% schema coverage the description must compensate, and it does so for the most ambiguous parameter: 'path' is explicitly relative to /v1beta1 with a concrete example including the colon-verb form. It adds nothing about how to choose between GET and POST beyond the method enum in the schema.

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?

States a specific action and resource: a raw passthrough call to the Play Developer Reporting API (v1beta1), with an example path. It implicitly separates itself from the other reporting_* siblings by being the escape hatch for 'anything not covered above', though it never explicitly distinguishes itself from the sibling raw_request.

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?

'For anything not covered above' plus the stated example gives a clear condition that selects this tool over the dedicated reporting_* wrappers. It also flags a mode condition ('allowed in read-only mode'), but it gives no explicit when-not guidance or names the alternative to prefer.

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

Deploy Server