Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Track

create_track

Create a custom closed-testing track for your app. Set up additional named tracks beyond internal, alpha, beta, and production to manage testing groups.

Instructions

Create a custom closed-testing track.

The four built-in tracks (internal, alpha, beta, production) always exist. This creates an additional named track, which is how closed testing groups beyond the built-ins are set up.

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": {
      "package_name": "<package_name>",
      "track": "<track>"
    },
    "name": "create_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesName for the new track
releasesNoOptional initial release configuration for the track
package_nameYesApp package name (e.g., com.example.myapp)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that this creates a new named track and that built-ins already exist, which is useful behavioral context. However, it does not mention side effects, prerequisites such as an open edit, idempotency, or what happens if the track already exists.

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?

The description is three short sentences with no wasted words. The main action is front-loaded, and the following sentences provide essential context about built-in tracks and closed testing groups without redundancy.

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 simple create tool with full schema coverage and an output schema, the description covers the essential context: what is created, why it exists, and how it relates to built-in tracks. It does not explain return values, but the output schema handles that, and there are no complex prerequisites mentioned that would be necessary to call it correctly.

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 the schema already documents both required parameters and the optional releases field. The description adds no parameter-level meaning beyond calling the track 'named' and 'custom,' so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Create a custom closed-testing track.' It also differentiates this from the four built-in tracks and clarifies that this tool creates an additional named track, which clearly distinguishes it from update_track and other track-related siblings.

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

Usage Guidelines4/5

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

The description implies the appropriate use case: when a closed testing group beyond the built-in tracks is needed. It does not explicitly name alternatives or say when not to use it, but it provides enough context by stating that built-in tracks always exist.

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