Google Play MCP

reporting_query_metric_set

Queries Android vitals metric sets from the Play Developer Reporting API to retrieve crash rates, ANR rates, error counts, and performance data for a given app package.

Instructions

Query an Android vitals metric set from the OPTIONAL Play Developer Reporting API (crash rate, ANR rate, error counts, slow start/rendering, wakeups, wakelocks, LMK). query is the request body: { timelineSpec: { aggregationPeriod: 'DAILY', startTime: { year, month, day, timeZone: { id: 'America/Los_Angeles' } }, endTime: {...} }, metrics: ['crashRate', 'distinctUsers'], dimensions: ['versionCode'], filter?, pageSize? }. Use reporting_get_metric_set first to see the freshness window. 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>",
      "metricSet": "<metricSet>",
      "query": "<query>"
    },
    "name": "reporting_query_metric_set"
  }
}

Input Schema

Name	Required	Description
`query`	Yes	Query body (timelineSpec, metrics, dimensions, filter, pageSize, pageToken)
`metricSet`	Yes
`packageName`	Yes	Application id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden; it does disclose 'Read-only' and flags the API as optional/enablement-gated, which is meaningful. It does not cover pagination behavior beyond the pageSize mention, rate limits, or what an empty result means — gaps for a query tool that can silently return partial pages.

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?

Two front-loaded sentences plus an inline example; every element (metric list, request shape, prerequisite, read-only) carries information. The parenthetical metric enumeration is slightly redundant with the metricSet enum but stays short.

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 3-parameter tool with a nested request body and no output schema, the description supplies the body structure, the freshness prerequisite, and the safety profile. Return value shape and pagination semantics remain undescribed, but the core invocation knowledge is present.

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?

Schema coverage is 67% and the query parameter is documented only as 'Query body (timelineSpec, metrics, dimensions, filter, pageSize, pageToken)'. The description adds substantial meaning: a concrete JSON skeleton with aggregationPeriod, time zone id, metric names, and dimension names, which the schema does not provide.

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?

Opens with a specific verb and resource ('Query an Android vitals metric set') and enumerates the metric families covered, so an agent can tell it apart from generic reporting tools. Differentiates from reporting_get_metric_set by action (fetch data vs. inspect freshness), though the sentence mixes resource listing with an implementation note ('OPTIONAL Play Developer Reporting API').

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 says to call reporting_get_metric_set first to see the freshness window, which is a real prerequisite that prevents empty/failed queries. No when-not guidance (e.g. what to use for non-vitals or cross-app queries), so not a 5.

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

Deploy Server