Skip to main content
Glama
AgiMaulana

Google Play Console

by AgiMaulana
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_track_info

Get release track details: status, rollout percentage, version codes, release notes, and country availability for any track (internal, alpha, beta, production).

Instructions

Get detailed info for a specific release track.

Returns releases with status, rollout %, version codes, release notes, and country availability.

Args: package_name: Package name, e.g. com.example.myapp track: "internal", "alpha", "beta", or "production". Default "production".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackNoproduction
package_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_track_infoOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.5.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided; description implies read-only via 'Get' but does not explicitly confirm non-destructive behavior. Lists return fields but omits side effects or permissions.

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 concise sentences plus clear Args block. Purpose front-loaded, no 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?

Lists return fields (status, rollout %, version codes, etc.) compensating for missing output schema. Could note that data is for latest release, but otherwise complete for a simple read operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Description adds example for package_name and valid values with default for track, going beyond schema. Despite context signal of 0% coverage, the Args block provides full parameter description.

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?

Clearly states 'Get detailed info for a specific release track' with specific verb and resource. Distinguishes from sibling 'list_tracks' which likely lists tracks without details.

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?

Does not provide when-to-use or when-not-to-use compared to siblings. No guidance on selecting this tool over alternatives like 'list_tracks'.

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