Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

halt_rollout

Stop a staged rollout from reaching new users while existing installs keep it. Use this emergency brake to halt distribution on a track, defaulting to production.

Instructions

Halt a staged rollout: stop serving the staged release to new users (existing installs keep it). The emergency brake — it is NOT blocked by PLAY_MCP_ALLOW_PRODUCTION_RELEASE=false (only by read-only mode). Track defaults to production.

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": "halt_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 inProgress release
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.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses that existing installs retain the release, that the PLAY_MCP_ALLOW_PRODUCTION_RELEASE=false guard does not block it, and that only read-only mode does. It stops short of saying whether the halt is reversible via resume_rollout or what permissions/response are involved.

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 the action and scope, then the environment caveat. No filler, and the parenthetical about existing installs is doing real work rather than being decorative.

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 six-parameter mutation tool with no annotations or output schema, the definition covers the crucial non-obvious facts (default track, environment-flag exemption, blast radius). Remaining gaps such as reversibility and the interaction with an open edit are handled adequately by the schema's own editId description.

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 versionCode, editId, dryRun and changesNotSentForReview are already documented in structured fields and the description adds nothing to them. The only param-adjacent content, 'track defaults to production', merely restates the schema default. Baseline 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?

States a specific verb and resource (halt a staged rollout) and immediately defines the exact scope: stopped for new users, existing installs keep the release. That scope line alone lets an agent distinguish this from resume_rollout and complete_rollout without opening any 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?

Frames itself explicitly as 'the emergency brake', which tells the agent this is the interrupt path rather than the normal rollout progression. It does not name resume_rollout or complete_rollout as alternatives, so the when-not guidance is implied rather than stated.

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