google-cloud-console-mcp

List release tracks

play_list_tracks

List all release tracks for an app in a Google Play edit, showing versionCodes and rollout status for internal, alpha, beta, production, and custom tracks.

Instructions

Lists all release tracks (internal, alpha, beta, production, and any custom tracks) for an app within an edit, including which versionCodes are on each and their rollout status.

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>"
    },
    "name": "play_list_tracks"
  }
}

Input Schema

Name	Required	Description	Default
`editId`	Yes	Edit id returned by play_create_edit
`packageName`	Yes	Play Console package name, e.g. "com.example.app"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does disclose the payload contents (versionCodes and rollout status), implying a read-only listing. However, it says nothing about permissions, edit-scope requirements, or pagination/result size, leaving real gaps for a no-annotation 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?

A single front-loaded sentence that covers scope, enumerated track types, and return contents with no wasted 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?

Since there is no output schema, the description usefully describes what is returned (versionCodes per track and rollout status), and the two required parameters are fully documented in the schema. Only auth/permission context and pagination behavior are missing.

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% and both parameters are documented in the schema, so the baseline is 3. The description adds no syntax or format detail beyond what the schema already conveys.

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?

States a specific verb ('Lists') and resource ('release tracks'), enumerates the track types covered, and adds scope ('for an app within an edit'). It implicitly separates itself from play_get_track (singular) via 'all', but does not name that sibling explicitly.

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?

Usage is only implied: 'within an edit' signals the tool belongs inside an edit session created by play_create_edit, but no when-to-use/when-not guidance or alternative (e.g. play_get_track for a single track) is stated.

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

Deploy Server