app-publish-mcp

google_halt_release

Halt an in-progress or completed Google Play release by package, track and version codes. Halting a completed production release rolls users back to the previous completed release.

Instructions

Halt an exact in-progress or completed release; halting a completed production release rolls users back to the previous completed release

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": {
      "packageName": "<packageName>",
      "editId": "<editId>",
      "track": "<track>",
      "versionCodes": "<versionCodes>"
    },
    "name": "google_halt_release"
  }
}

Input Schema

Name	Required	Description
`track`	Yes	Track ID returned by google_list_tracks
`editId`	Yes	Edit ID
`packageName`	Yes	Android package name
`versionCodes`	Yes	Complete version-code set identifying the release to halt

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.0Oct 25, 2026

changedInput schema / properties / track / description

Previous value: -"Track name"New value: +"Track ID returned by google_list_tracks"

addedInput schema / properties / track / minLength
```
Added value: +1
```

addedInput schema / properties / versionCodes

Added value: +{
+  "description": "Complete version-code set identifying the release to halt",
+  "items": {
+    "pattern": "^[1-9]\\d*$",
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "packageName",
-  "editId",
-  "track"
-]New value: +[
+  "packageName",
+  "editId",
+  "track",
+  "versionCodes"
+]

First observedv0.3.1Mar 19, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical side effect: halting a completed production release rolls users back to the previous completed release. It still omits permission requirements, reversibility details, and edit lifecycle requirements.

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?

The description is a single compact sentence with the action front-loaded and the key rollback consequence attached. Every part earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with no annotations and no output schema, the description covers purpose and one major side effect but leaves out workflow context such as needing an open edit and committing it afterward. It is adequate but incomplete for safe invocation.

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 schema already documents all four required parameters. The description reinforces the idea of an 'exact release' but does not add parameter-level syntax or constraints beyond what the schema provides.

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 description states a specific verb and resource: 'Halt ... release.' It scopes the operation to an 'exact in-progress or completed release,' which clearly distinguishes it from create/promote release siblings.

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?

It gives a usable condition by saying the release must be in-progress or completed, and notes the completed-production rollback effect. However, it does not name alternatives such as promote_release or create_release, nor does it state when not to use it or what edit prerequisite is required.

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

Deploy Server