Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Halt Release

halt_release

Halt a staged rollout on Google Play immediately, without confirmation, to stop the release during an incident. This safety operation takes effect right away and is written to the audit log.

Instructions

Halt a staged rollout. Takes effect immediately, no confirmation needed.

Deliberately NOT behind the confirmation gate. Halting is the one operation that makes things safer, and demanding a second round-trip during an incident is itself the failure mode. It is still written to the audit log.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package_name": "<package_name>",
      "track": "<track>",
      "version_code": "<version_code>"
    },
    "name": "halt_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesTrack containing the release (internal, alpha, beta, production)
package_nameYesApp package name
version_codeYesVersion code of the release to halt

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that the action takes effect immediately, requires no confirmation, deliberately bypasses the confirmation gate, and is still written to the audit log. It could add more about reversibility or failure conditions, but the major behavioral traits are well covered.

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 core instruction is front-loaded in the first sentence. The following sentences add valuable context about the confirmation gate and audit logging, though there is slight redundancy between 'no confirmation needed' and 'Deliberately NOT behind the confirmation gate.' Overall, every sentence contributes to understanding the tool's behavior.

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?

The tool has an output schema, so return values do not need to be described in prose. Given the simple three-parameter operation, the description covers the essential behavior, context, and safety implications. It is reasonably complete, though a note about whether halting is reversible would strengthen it further.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents all three parameters. The description adds no additional parameter-level meaning beyond what the schema provides, making the baseline score of 3 appropriate.

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?

The opening sentence 'Halt a staged rollout' uses a specific verb and resource, clearly stating the action. It naturally distinguishes itself from sibling tools like promote_release or update_rollout by focusing on halting rather than progressing or modifying a rollout.

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?

The description clearly implies when to use this tool: during incidents or when a rollout needs to be stopped immediately. It explains the deliberate exception to the confirmation gate and emphasizes the safety rationale, but it does not explicitly name alternatives or state when not to use it.

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

Deploy Server

Other Tools