app-publish-mcp

google_get_track

Retrieve details for a specific Google Play release track using package name, edit ID, and track ID to inspect rollout status and configuration.

Instructions

Get details of a specific release track

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

Input Schema

Name	Required	Description
`track`	Yes	Track ID returned by google_list_tracks
`editId`	Yes	Edit ID
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.7.0Oct 25, 2026
- changedInput schema / properties / track / description
```
Previous value: -"Track name"New value: +"Track ID returned by google_list_tracks"
```
- removedInput schema / properties / track / enum
```
Removed value: -[
-  "internal",
-  "alpha",
-  "beta",
-  "production"
-]
```
- addedInput schema / properties / track / minLength
```
Added value: +1
```
First observedv0.3.1Mar 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies read-only, but the description does not confirm safety, note that an editId must exist, or describe what the response contains. It adds essentially nothing about behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single efficient sentence with no waste, but it is terse enough that it omits information an agent needs. Concise at the cost of under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-required-parameter tool with no annotations and no output schema, the description should at least explain the edit prerequisite and what the details are. Neither is covered, leaving meaningful gaps.

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 all three parameters (track, editId, packageName) are already documented in the schema. The description adds no format or constraint details beyond that, so baseline 3 applies.

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 (get) and resource (release track), and the singular 'a specific release track' does distinguish it from the plural google_list_tracks sibling. However, 'details' is vague about what is actually returned.

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

Usage Guidelines2/5

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

No indication of when to use this versus google_list_tracks, nor any mention of prerequisites such as needing an active edit (editId) first. The agent must infer the edit-lifecycle context from sibling names alone.

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

Deploy Server