Google Play MCP

promote_release

Move an Android build between Google Play tracks, such as internal to beta or beta to production, carrying version codes and release notes, with staged rollout and dry-run validation options.

Instructions

Promote a build from one track to another (e.g. internal → beta, beta → production), carrying its versionCodes and release notes. By default promotes the newest release on fromTrack as a full rollout; pass status:'inProgress' + userFraction for a staged rollout, or 'draft' to stage it. Promoting to production is gated by PLAY_MCP_ALLOW_PRODUCTION_RELEASE. Set dryRun:true to validate without publishing.

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>",
      "fromTrack": "<fromTrack>",
      "toTrack": "<toTrack>"
    },
    "name": "promote_release"
  }
}

Input Schema

Name	Required	Description
`dryRun`	No	Preview only: open a temporary edit, apply, validate, then delete it. Nothing is published (default false). Ignored when editId is set.
`editId`	No	Optional: an open edit from insert_edit. The change is applied inside that edit and NOT committed — batch several changes, then call commit_edit.
`status`	No	Default 'completed'
`toTrack`	Yes	Track name: internal, alpha (closed testing), beta (open testing), production, a custom closed-testing track name, or a form-factor track such as wear:production
`fromTrack`	Yes	Track name: internal, alpha (closed testing), beta (open testing), production, a custom closed-testing track name, or a form-factor track such as wear:production
`packageName`	Yes	Application id (package name), e.g. com.example.app
`versionCode`	No	Promote the release containing this version code (default: the newest release)
`releaseNotes`	No	Override the notes (default: copy from the source release)
`userFraction`	No	For status inProgress: 0 < fraction < 1
`changesNotSentForReview`	No	Commit 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.

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 burden and does disclose the key gating behavior (production requires PLAY_MCP_ALLOW_PRODUCTION_RELEASE) and the non-publishing dryRun mode. It omits what happens to the source track's release after promotion and does not state permission requirements or the irreversibility of publishing to production.

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 front-loaded sentences: core action first, then rollout modes, then safety gates. Every clause carries operational information and nothing is repeated from the name or 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 10-parameter mutation tool with no annotations and no output schema, the description covers the critical decision points (default vs staged vs draft, production gating, dry run). The edit-batching workflow and commit-review flag are left entirely to schema descriptions, which handle them adequately.

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 100%, so baseline would be 3, but the description adds real meaning: 'status inProgress + userFraction for a staged rollout' explains how two parameters interact, and 'default promotes the newest release' clarifies versionCode omission. It does not explain editId batching or changesNotSentForReview, which remain schema-only.

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?

The description gives a specific verb and resource ('Promote a build from one track to another') with concrete examples (internal → beta, beta → production) and names the data carried (versionCodes, release notes). This clearly separates it from a creation tool like create_release, though no sibling is named explicitly.

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?

It states the default behavior (newest release as a full rollout) and the two mode switches: status:'inProgress' + userFraction for staged rollout, or 'draft' to stage it. It signals a production precondition (PLAY_MCP_ALLOW_PRODUCTION_RELEASE) and dryRun for validation, but never says when to prefer create_release or complete_rollout over this tool.

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

Deploy Server