Skip to main content
Glama

update_release

Modify rollout percentage or status of an existing Google Play app release to control distribution, including increasing, halting, resuming, or completing deployments.

Instructions

Update rollout percentage and/or status of an existing release.

Examples: increase rollout (rollout_percentage=50), complete (=100), halt (status="halted"), resume (status="inProgress").

NOTE: With Managed Publishing enabled, changes are held pending approval. Call publish_managed_release to send live.

Args: package_name: Package name, e.g. com.example.myapp track: Track to update. Default "production". rollout_percentage: New rollout % (0–100). Pass 100 to complete. status: "inProgress", "halted", "completed", or "draft". version_codes: Filter to release containing these codes. Default: first release found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
trackNoproduction
rollout_percentageNo
statusNo
version_codesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler for the update_release tool.
    @mcp.tool()
    def update_release(
        package_name: str,
        track: str = "production",
        rollout_percentage: Optional[float] = None,
        status: Optional[str] = None,
        version_codes: Optional[list[int]] = None,
    ) -> str:
        """Update rollout percentage and/or status of an existing release.
    
        Examples: increase rollout (rollout_percentage=50), complete (=100),
        halt (status="halted"), resume (status="inProgress").
    
        NOTE: With Managed Publishing enabled, changes are held pending approval.
        Call publish_managed_release to send live.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
            track: Track to update. Default "production".
            rollout_percentage: New rollout % (0–100). Pass 100 to complete.
            status: "inProgress", "halted", "completed", or "draft".
            version_codes: Filter to release containing these codes. Default: first release found.
        """
        try:
            result = _publisher().update_release(
                package_name=package_name,
                track=track,
                rollout_percentage=rollout_percentage,
                version_codes=version_codes,
                status=status,
            )
            return json.dumps(
                {
                    "success": True,
                    "message": "Release updated successfully.",
                    "track": _format_track(result["track"]),
                    "editId": result.get("commit", {}).get("editId"),
                },
                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. Discloses critical workflow behavior: changes are held pending approval when Managed Publishing is enabled. Explains business logic (100 = complete). Does not mention auth requirements or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with purpose first, followed by concrete examples, important workflow note, then Args section. The Args section is necessary given zero schema coverage and adds no wasted words. Examples are concise and immediately illustrative.

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?

Given 5 parameters with complex domain logic (release management) and zero schema annotations, the description comprehensively covers parameter semantics and key workflow constraints (Managed Publishing). Output schema exists, so return values need not be described.

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?

Schema has 0% description coverage. Description fully compensates by documenting all 5 parameters: package_name includes format example ('com.example.myapp'), status lists valid enum values, rollout_percentage specifies range (0-100) and semantics, version_codes explains filtering logic ('Default: first release found').

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 ('Update') targeting a specific resource ('existing release') with defined scope ('rollout percentage and/or status'). The opening sentence immediately distinguishes this from 'create_release' by specifying 'existing'.

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?

Provides concrete usage patterns via examples ('increase rollout', 'complete', 'halt'). Explicitly names sibling tool 'publish_managed_release' as the next step when Managed Publishing is enabled. Lacks explicit contrast with 'create_release' or 'promote_release'.

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