Skip to main content
Glama

get_track_info

Retrieve detailed release track information including status, rollout percentage, version codes, release notes, and country availability for Google Play Console apps.

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
package_nameYes
trackNoproduction

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_track_info tool, which fetches track data using the publisher service and formats it.
    def get_track_info(
        package_name: str,
        track: str = "production",
    ) -> str:
        """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".
        """
        try:
            track_data = _publisher().get_track(package_name, track)
            formatted = _format_track(track_data)
            releases = formatted["releases"]
    
            statuses = {r["status"] for r in releases if r["status"]}
            if "inProgress" in statuses:
                summary = "Staged rollout in progress."
            elif "draft" in statuses:
                summary = "Release is in draft / under Google Play review."
            elif "halted" in statuses:
                summary = "Rollout is halted."
            elif statuses == {"completed"}:
                summary = "Release fully rolled out (100%)."
            else:
                summary = f"Status: {', '.join(statuses)}" if statuses else "No active releases."
    
            return json.dumps(
                {
                    "packageName": package_name,
                    "summary": summary,
                    **formatted,
                },
                indent=2,
            )
Behavior3/5

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

No annotations provided, so description carries full burden. Compensates partially by disclosing return fields (status, rollout %, version codes, release notes, country availability) which helps agents understand data richness. However, omits safety profile (read-only vs destructive), error handling (what if track invalid?), and idempotency.

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?

Well-structured with purpose front-loaded, followed by return value summary and Args section. No wasted words; every sentence earns its place by conveying distinct information not present in schema or siblings.

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 2-parameter read operation with simple types. Since output schema exists, the description doesn't need exhaustive return documentation, though it helpfully summarizes key fields. Could improve by mentioning error conditions (e.g., invalid package name).

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

Parameters5/5

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

Excellent compensation for 0% schema description coverage. Description provides concrete example for package_name ('com.example.myapp') and explicit allowed values plus default for track ('internal', 'alpha', 'beta', 'production' - Default 'production'), effectively documenting both parameters.

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?

Clear verb ('Get detailed info') and resource ('release track') with scope implied by 'specific'. Distinguishes from list_tracks (which lists all tracks) by focusing on one track. However, could better contextualize against monitoring siblings (get_crash_rate, get_vitals_summary) which also return 'info' but different types.

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?

Provides implied usage by documenting valid track values (internal, alpha, beta, production) and default behavior. However, lacks explicit guidance on when to use this vs list_tracks or when to prefer vitals/monitoring tools that also query track data.

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