Skip to main content
Glama

promote_release

Move app releases between Google Play Console tracks like internal, alpha, beta, and production. Copy version codes and manage rollout percentages for staged releases.

Instructions

Promote a release from one track to another.

Copies version codes from source to destination. Common: internal→alpha→beta→production. Release notes/name are inherited unless overridden.

Args: package_name: Package name, e.g. com.example.myapp from_track: Source — "internal", "alpha", or "beta". to_track: Destination — "alpha", "beta", or "production". version_codes: Version codes to promote, e.g. [1234]. rollout_percentage: Rollout % at destination. Default 10%. Use 100 for full release. release_name: Optional name override. release_notes: Optional {lang: text} override, e.g. {"en-US": "New features"}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
package_nameYes
from_trackYes
to_trackYes
version_codesYes
rollout_percentageNo
release_nameNo
release_notesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool handler for "promote_release", which takes arguments and calls the underlying client's promote_release method.
    def promote_release(
        package_name: str,
        from_track: str,
        to_track: str,
        version_codes: list[int],
        rollout_percentage: float = 10.0,
        release_name: str = "",
        release_notes: Optional[dict] = None,
    ) -> str:
        """Promote a release from one track to another.
    
        Copies version codes from source to destination. Common: internal→alpha→beta→production.
        Release notes/name are inherited unless overridden.
    
        Args:
            package_name: Package name, e.g. com.example.myapp
            from_track: Source — "internal", "alpha", or "beta".
            to_track: Destination — "alpha", "beta", or "production".
            version_codes: Version codes to promote, e.g. [1234].
            rollout_percentage: Rollout % at destination. Default 10%. Use 100 for full release.
            release_name: Optional name override.
            release_notes: Optional {lang: text} override, e.g. {"en-US": "New features"}.
        """
        try:
            notes = _notes_from_dict(release_notes)
            result = _publisher().promote_release(
                package_name=package_name,
                from_track=from_track,
                to_track=to_track,
                version_codes=version_codes,
                rollout_percentage=rollout_percentage,
                release_name=release_name or None,
                release_notes=notes,
            )
            return json.dumps(
                {
                    "success": True,
                    "message": (
                        f"Version codes {version_codes} promoted from '{from_track}' "
                        f"to '{to_track}' at {rollout_percentage}% rollout."
                    ),
                    "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)
  • The implementation of the promote_release logic, which interacts with the Google Play Developer API to copy a release between tracks.
    def promote_release(
        self,
        package_name: str,
        from_track: str,
        to_track: str,
        version_codes: List[int],
        rollout_percentage: float = 10.0,
        release_name: Optional[str] = None,
        release_notes: Optional[List[Dict[str, str]]] = None,
    ) -> Dict[str, Any]:
        """Copy a release from one track to another.
    
        Release notes and name are inherited from the source release unless
        overridden. rollout_percentage applies when to_track is production.
        """
        if not (0 < rollout_percentage <= 100):
            raise ValueError("rollout_percentage must be > 0 and <= 100.")
    
        edit_id = self._create_edit(package_name)
        try:
            src_releases = self._get_track(
                package_name, edit_id, from_track
            ).get("releases", [])
            target_vcs = {str(vc) for vc in version_codes}
            src = next(
                (
                    r for r in src_releases
                    if set(r.get("versionCodes", [])).intersection(target_vcs)
                ),
                None,
            )
            notes = release_notes or (src.get("releaseNotes") if src else None)
            name = release_name or (src.get("name") if src else None)
    
            release: Dict[str, Any] = {
                "versionCodes": [str(vc) for vc in version_codes],
                "status": "completed" if rollout_percentage >= 100 else "inProgress",
            }
            if rollout_percentage < 100:
                release["userFraction"] = round(rollout_percentage / 100.0, 4)
            if name:
                release["name"] = name
            if notes:
                release["releaseNotes"] = notes
    
            updated_track = self._update_track(
                package_name, edit_id, to_track,
                {"track": to_track, "releases": [release]}
            )
            commit = self._commit_edit(package_name, edit_id)
            return {"track": updated_track, "commit": commit}
        except Exception:
            self._delete_edit(package_name, edit_id)
            raise
Behavior3/5

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

With no annotations provided, the description carries the full burden. It successfully explains key mechanics: that version codes are copied (not moved), and that release notes/name are inherited unless overridden. However, it omits critical safety disclosures for a mutation tool—such as what happens to existing releases in the destination track, whether the operation is reversible, or warnings about promoting directly to production.

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?

The description is well-structured with clear front-loading: the first sentence summarizes the operation, the second explains mechanics, and the bulleted Args section provides necessary parameter details. Each sentence earns its place. It is slightly verbose due to the required Args documentation, but this is necessary given the zero-coverage schema.

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 the 7-parameter complexity and 0% schema coverage, the description successfully documents all parameters through the Args section. It explains the domain-specific track promotion workflow and inheritance behavior. Since an output schema exists, omitting return value details is acceptable. It could improve by mentioning error conditions or source track behavior post-promotion.

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?

With 0% schema description coverage, the description fully compensates via the 'Args' section. Every parameter is documented with semantic meaning (e.g., 'Source', 'Destination'), valid value hints ('internal', 'alpha', 'beta', 'production'), and concrete examples (e.g., [1234], {"en-US": "New features"}). This exceeds the baseline requirement given the schema deficit.

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?

The description opens with a specific verb ('Promote') and resource ('release'), clearly defining the core operation. The phrase 'from one track to another' establishes scope, while 'Copies version codes' explains the mechanism. The 'Common: internal→alpha→beta→production' example implicitly distinguishes this from sibling tools like create_release or upload_artifact by focusing on track progression workflows.

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?

The 'Common' line provides an implied usage pattern (internal→alpha→beta→production), giving context for the promotion workflow. However, it lacks explicit guidance on when to choose this over siblings like create_release or update_release, and does not specify prerequisites (e.g., that the version codes must already exist in the source track).

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