Google Play MCP

list_tracks

List every app track (internal, alpha, beta, production, custom, form-factor) with release status, version codes, user fraction, and notes; read-only, with optional open-edit context.

Instructions

List every track of an app (internal, alpha, beta, production, custom and form-factor tracks) with their releases: status, versionCodes, userFraction, release notes. Read-only.

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

Input Schema

Name	Required	Description	Default
`editId`	No	Optional: read from this open edit (to see uncommitted changes). Without it a temporary edit is opened and deleted.
`packageName`	Yes	Application id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/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 behavioral burden. It usefully states 'Read-only' and lists the release fields returned, but it does not mention permissions, rate limits, or that the operation may open and delete a temporary edit when editId is omitted; that side effect appears only in the schema.

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 tight sentences with no wasted wording. The main scope is front-loaded, the returned fields are summarized briefly, and the read-only note closes the description cleanly.

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 tool is simple, the input schema fully documents its two parameters, and the description summarizes the release fields returned despite there being no output schema. It is nearly complete, with only the temporary-edit side effect left to the schema rather than the 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 both packageName and editId are already documented in the input schema. The description adds no parameter-level meaning beyond saying it lists tracks for an app, which aligns with the baseline for fully covered parameters.

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 gives a specific verb and resource: list every track of an app, including the track types and release fields returned. This clearly distinguishes it from sibling list_* tools for apps, APKs, bundles, images, and other resources.

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 use case is implied by 'List every track of an app' and the returned releases, but there is no explicit when-to-use guidance, no mention of alternatives, and no exclusions. It is adequate but leaves selection to inference.

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

Deploy Server