google-play-developer-mcp

app_recovery_cancel

Cancel an in-flight app recovery action for an Android app by providing the package name and recovery ID.

Instructions

Cancel an in-flight app recovery action.

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>",
      "appRecoveryId": "<appRecoveryId>"
    },
    "name": "app_recovery_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`packageName`	Yes	Android application package name, e.g. com.example.app
`appRecoveryId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

B3.3/5.0

Behavior2/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 indicates the action is cancelling an in-flight recovery (a mutation), but it does not disclose behavioral traits such as whether it's destructive, reversible, required permissions, or what happens to related data. This is insufficient for a cancel operation.

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 concise sentence that is front-loaded with the key action and resource. Every word earns its place, with no unnecessary information.

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

Completeness2/5

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

Given no output schema and no annotations, the description lacks completeness. It does not explain the 'in-flight' state, expected response, error conditions, or prerequisites. A cancellation tool requires more context to ensure the agent understands the implications and lifecycle.

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

Parameters2/5

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

The description does not add any meaning beyond the input schema. While the schema describes packageName (50% coverage), appRecoveryId has no description. The description offers no insight into what appRecoveryId is or how to obtain it, leaving the agent without sufficient guidance.

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 'Cancel an in-flight app recovery action' clearly states the verb 'Cancel' and the resource 'app recovery action'. Among sibling tools like app_recovery_create, app_recovery_deploy, app_recovery_list, and app_recovery_add_targeting, this tool is uniquely identified as the cancellation action, providing excellent differentiation.

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 description implies usage when an app recovery action is in-flight and needs to be canceled, but it does not explicitly state when to use this tool over alternatives, nor does it provide when-not or exclusion criteria. The guidance is implied but not elaborated.

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

Deploy Server