Skip to main content
Glama

list_tracks

Retrieve all release tracks for a Google Play app to view rollout percentages, statuses, and country availability for internal, alpha, beta, and production channels.

Instructions

List all release tracks with their current releases.

Returns tracks (internal, alpha, beta, production) with rollout percentages, statuses, and country availability.

Args: package_name: Package name, e.g. com.example.myapp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler for the "list_tracks" MCP tool. It calls the PublisherClient's list_tracks method, formats the output, and returns a JSON string.
    @mcp.tool()
    def list_tracks(package_name: str) -> str:
        """List all release tracks with their current releases.
    
        Returns tracks (internal, alpha, beta, production) with rollout
        percentages, statuses, and country availability.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
        """
        try:
            data = _publisher().list_tracks(package_name)
            tracks = [_format_track(t) for t in data.get("tracks", [])]
            return json.dumps(
                {"packageName": package_name, "tracks": tracks},
                indent=2,
            )
        except Exception as exc:
            return json.dumps({"success": False, "error": str(exc)}, indent=2)
Behavior4/5

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

No annotations provided, so description carries full burden. It successfully discloses the read-only nature through 'List' and 'Returns', and details the output payload (rollout percentages, statuses, country availability, track types). Missing only explicit safety confirmations (idempotent, no side effects) or rate limit warnings.

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?

Efficient three-part structure: purpose statement, return value specification, and parameter documentation. Every sentence earns its place with zero redundancy. Front-loaded with the primary action.

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?

Appropriate for a single-parameter list operation with existing output schema. The description provides sufficient detail about the returned data structure without needing to replicate the output schema. Only gap is explicit sibling differentiation guidance.

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?

Schema coverage is 0% (parameter lacks description field), but the Args section compensates by documenting the single parameter with a clear example ('com.example.myapp') that clarifies expected format. This provides sufficient semantic context for the agent to invoke correctly.

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?

Clear specific verb ('List') + resource ('release tracks'), and explicitly scopes the operation to fetching current releases. The plural 'tracks' and 'list all' clearly distinguishes this from sibling 'get_track_info' which likely retrieves specific single-track details.

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?

No explicit when-to-use guidance or comparison to alternatives like 'get_track_info'. While the intent is clear from context, it lacks explicit direction on when to prefer this bulk listing versus retrieving individual track details.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AgiMaulana/GooglePlayConsoleMcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server