Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_track

Read one Google Play track and its releases—status, version codes, user fraction, and notes—to inspect rollout details or uncommitted changes.

Instructions

Read one track and its releases (status, versionCodes, userFraction, 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>",
      "track": "<track>"
    },
    "name": "get_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesTrack name: internal, alpha (closed testing), beta (open testing), production, a custom closed-testing track name, or a form-factor track such as wear:production
editIdNoOptional: read from this open edit (to see uncommitted changes). Without it a temporary edit is opened and deleted.
packageNameYesApplication id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description does real work by declaring 'Read-only', which tells the agent this call will not mutate the app. It does not disclose the notable side effect documented only in the schema — that omitting editId opens and then deletes a temporary edit — nor return shape beyond the field names listed.

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?

One front-loaded sentence stating the action and returned fields, plus a two-word safety marker. No filler, nothing to trim, and the most important information leads.

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 three-parameter read tool with no output schema, listing the key release fields gives the agent a good sense of the payload. The only meaningful gap is that the transient-edit side effect for the no-editId case is left entirely to the schema.

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 coverage is 100%, so packageName, track, and editId are already fully documented, including the track name taxonomy and the editId temp-edit behavior. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 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 and resource — 'Read one track and its releases' — and names the fields returned (status, versionCodes, userFraction, notes). It is clearly distinct from update_track by the read verb, though it never explicitly contrasts the two.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. An agent must infer from the verb alone that this is the read path versus update_track, and the description says nothing about when to supply editId (that lives only in the schema).

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

Deploy Server

Other Tools