Skip to main content
Glama

publish_managed_release

Deploy approved app updates to production in Google Play Console when Managed Publishing is active. Use after changes pass review to publish releases.

Instructions

Send approved changes live when Managed Publishing is enabled.

Call after changes committed via create_release/update_release/promote_release have been reviewed in Play Console. No-op if Managed Publishing is off.

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

  • MCP tool handler for 'publish_managed_release'. It uses the internal publisher client to execute the action and handles errors by returning a JSON response.
    @mcp.tool()
    def publish_managed_release(package_name: str) -> str:
        """Send approved changes live when Managed Publishing is enabled.
    
        Call after changes committed via create_release/update_release/promote_release
        have been reviewed in Play Console. No-op if Managed Publishing is off.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
        """
        try:
            _publisher().publish_managed_release(package_name)
            return json.dumps(
                {
                    "success": True,
                    "message": "Changes sent live successfully via Managed Publishing.",
                },
                indent=2,
            )
        except Exception as exc:
            return json.dumps({"success": False, "error": str(exc)}, indent=2)
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It successfully documents the 'no-op' behavior when Managed Publishing is disabled and mentions the human review requirement. However, it lacks disclosure about error conditions, timeout behavior, or the irreversible nature of publishing (critical for app store operations).

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?

Three sentences efficiently structured: purpose statement, workflow prerequisite, and behavioral condition. Every sentence earns its place. The Args section is appropriately separated and minimal. Information is front-loaded with the critical action verb.

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 this is a single-parameter workflow step with an existing output schema, the description adequately covers the lifecycle context. It correctly references prerequisite sibling tools and explains the Managed Publishing prerequisite. Minor gap: could briefly characterize the output (though schema exists).

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 description coverage is 0% (parameter has only title, no description field). The description compensates via the Args section by providing 'Package name, e.g. com.example.myapp', adding semantic meaning and format guidance for the single required parameter.

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?

Description clearly states the action ('Send approved changes live'), the specific condition ('when Managed Publishing is enabled'), and the domain (Play Console releases). It explicitly distinguishes this from sibling tools by stating it must be called 'after changes committed via create_release/update_release/promote_release', clearly positioning it as the final publishing step in a workflow sequence.

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

Usage Guidelines5/5

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

Provides explicit workflow guidance: 'Call after changes committed via... have been reviewed in Play Console' establishes exact prerequisites. Also includes explicit negative condition 'No-op if Managed Publishing is off', informing the agent when the tool will not perform the expected action.

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