Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

resume_rollout

Resume a halted Google Play rollout at its previous user fraction or set a new fraction; production is the default track.

Instructions

Resume a halted rollout at its previous fraction (or a new userFraction). Track defaults to production. Gated on production by PLAY_MCP_ALLOW_PRODUCTION_RELEASE.

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

Input Schema

NameRequiredDescriptionDefault
trackNoDefault 'production'
dryRunNoPreview only: open a temporary edit, apply, validate, then delete it. Nothing is published (default false). Ignored when editId is set.
editIdNoOptional: an open edit from insert_edit. The change is applied inside that edit and NOT committed — batch several changes, then call commit_edit.
packageNameYesApplication id (package name), e.g. com.example.app
versionCodeNoDefault: the halted release
userFractionNoOptional new fraction, 0 < fraction < 1
changesNotSentForReviewNoCommit option: keep the changes out of review until sent from Play Console. Google requires this for some apps and rejects it for others — set it only if a commit error asks for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/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 usefully discloses the production gating via PLAY_MCP_ALLOW_PRODUCTION_RELEASE and the production track default, which are non-obvious operational traits, but it says nothing about permissions, reversibility, or what happens if the rollout is not actually halted — significant gaps for a mutating release tool.

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, each carrying distinct information: the action and its default, the track default, and the environment gate. The most important constraint (resume at previous fraction) is front-loaded and there is no redundant wording.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the critical global context — default track and the production environment gate — while the rich schema handles per-parameter detail. The remaining gap is behavioral: nothing about failure modes or whether a resume is reversible.

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 every parameter, including the editId batching and dryRun preview semantics. The description only adds the meaning of userFraction and the track default, which largely restates schema content, so the baseline of 3 applies.

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 opens with a specific verb+resource: "Resume a halted rollout," which cleanly separates it from halt_rollout, complete_rollout, and set_rollout_fraction. It also states the default behavior (resume at previous fraction) and the override path (new userFraction), so an agent knows exactly what the call does without opening the schema.

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?

The description establishes the precondition clearly (the rollout must be halted) and states the default track is production. It implies the relationship to set_rollout_fraction via "or a new userFraction" but never names an alternative tool or says explicitly when to prefer one over the other, so it stops short of full routing guidance.

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