google-play-developer-mcp

tracks_update

Update an app's release track on Google Play by replacing its releases with new version codes, statuses, rollout fractions, and notes.

Instructions

Full replacement of track state. releases is an array of release objects — versionCodes, status (draft|inProgress|halted|completed), userFraction (0-1 for staged rollout), inAppUpdatePriority (0-5), countryTargeting, and releaseNotes.

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>",
      "editId": "<editId>",
      "track": "<track>",
      "releases": "<releases>"
    },
    "name": "tracks_update"
  }
}

Input Schema

Name	Required	Description
`track`	Yes	Track name: internal, alpha, beta, production — or a custom closed-testing track id
`editId`	Yes	Edit id returned by `edits_insert` — required for all edits.* writes
`releases`	Yes
`packageName`	Yes	Android application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations provided, so the description must carry the behavioral transparency burden. It states 'full replacement' but does not disclose side effects (e.g., whether previous releases are lost permanently), required permissions, or if the operation is reversible. This is insufficient for a mutation 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?

Two sentences: the first states the action concisely, the second details the most complex parameter. No unnecessary words, and information is front-loaded. Every sentence earns its place.

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?

The description covers the core action and the releases parameter well. However, it omits details about return values (no output schema) and does not mention the requirement for an active edit context (though schema hints at it). For a tool with four required params, this is mostly complete.

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?

The schema covers packageName, editId, and track with descriptions, leaving releases undocumented. The description fills this gap by detailing the structure of releases objects (versionCodes, status, userFraction, etc.), adding significant value beyond the schema.

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 clearly states 'Full replacement of track state,' which is specific and distinguishes from sibling tools like tracks_patch (partial update) and tracks_create (new track). The verb 'replacement' and resource 'track state' are precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for complete overwrite but does not explicitly guide when to use vs alternatives like tracks_patch. No mention of context or prerequisites (e.g., need for an edit). This is adequate but leaves room for ambiguity.

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

Deploy Server