google-play-vitals-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_PLAY_CACHE_TTL | No | Cache duration in seconds (default: 300). | 300 |
| GOOGLE_PLAY_PACKAGE_NAME | No | Default Android application package name (e.g., com.example.app). | |
| GOOGLE_PLAY_CREDENTIALS_JSON | No | Raw JSON string of Service Account credentials. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to Google Cloud Service Account JSON key file. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| play_check_statusC | Verify Google Play API dependencies, GCP Service Account credentials, and environment readiness. |
| play_get_release_tracksA | [Release Discovery] Fetch Google Play release tracks (PRODUCTION, BETA, ALPHA, INTERNAL) and active serving releases with their release names and versionCodes. Essential for automatically discovering the latest production version. |
| play_search_error_issuesB | [Atomic Issue Cluster Search] Search Google Play error clusters (CRASH, ANR, or NON_FATAL) with full AIP-160 filter support. Filter by specific versionCode, user-perceived state, or process state (FOREGROUND/BACKGROUND). Sorted by user impact and occurrences. |
| play_get_error_reportsB | [Atomic Error Reports & Stack Traces] Fetch detailed multi-device sample reports and cleaned de-obfuscated stack traces for a given error issue ID or resource name. |
| play_list_anomaliesA | [Anomaly Detection] List production metric anomalies and sudden regression spikes detected by Google Play algorithms for the application. |
| play_list_accessible_appsB | [Account Apps Discovery] List all Google Play applications accessible by the configured GCP Service Account. |
| play_get_top_anr_summaryA | [One-shot Diagnosis] Retrieve top ANR error clusters along with affected user counts, occurrence rates, and representative cleaned main-thread stack traces. Eliminates back-and-forth round trips. |
| play_get_metric_trendsB | [Token-efficient Metrics] Query trends and daily averages for ANR rate, slow cold start rate (Baseline Profile verification), or Crash rate. Redundant Protobuf metadata is stripped. |
| play_compare_versionsA | [Version Comparison] Compare metrics between two app versions (e.g., before and after Baseline Profile / ANR fixes). Automatically calculates delta and percentage improvement. |
| play_get_raw_error_reportsA | [Deep-dive Drilldown] Fetch multi-device environmental samples and full stack traces for a specific error issue ID. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-anr-incident | Interactive diagnostic prompt to analyze top production ANR clusters, interpret stack traces, and recommend concrete architectural fixes. |
| verify-baseline-profile | Audit release performance comparing baseline vs. target version to verify Baseline Profile cold-startup acceleration and ANR reductions. |
| vitals-weekly-report | Generate a comprehensive markdown report summarizing weekly Android Vitals trends (ANR rate, crash rate, slow cold start rate). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Google Play Vitals System & Environment Status | Real-time diagnostic overview of dependencies, active package configuration, and GCP credentials. |
TDQS
Scored across 10 tools
Tools are largely distinct, each targeting a specific aspect of Google Play Vitals (status, releases, errors, anomalies, metrics, versions). The only potential confusion is between play_get_error_reports and play_get_raw_error_reports, but the descriptions clarify different levels of detail (cleaned vs. raw).
All tools follow a consistent 'play_' prefix with snake_case verb_noun patterns (e.g., list_anomalies, compare_versions, get_metric_trends). There are no mixed conventions or ambiguous verbs, making the naming highly predictable.
With 10 tools, the server is well-scoped for its purpose. Each tool adds value—covering discovery, error analysis, metrics, and anomaly detection—without redundancy or overwhelming bloat. The count fits comfortably within the ideal 3-15 range.
The tool set covers the main workflows for monitoring Google Play Vitals: release tracking, error cluster search, detailed reports, ANR summaries, metric trends, and version comparisons. Minor gaps exist (e.g., no dedicated tool for fetching specific version metrics), but agents can work around them using existing tools.