Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Deploy App Recovery

deploy_app_recovery

Deploy an app recovery action to users by specifying the package name and recovery ID. Use this to roll out fixes or mitigations for app issues.

Instructions

Deploy an app recovery action to users.

Disabled in read-only mode.

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>",
      "app_recovery_id": "<app_recovery_id>"
    },
    "name": "deploy_app_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
package_nameYesApp package name
app_recovery_idYesApp recovery action ID
confirmation_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it only adds 'Disabled in read-only mode' and a generic deploy statement. It does not disclose side effects, whether confirmation is required, reversibility, or any authorization implications, leaving key operational behavior implicit.

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 short and front-loaded: the first sentence states the action and target, the second adds a useful constraint. Both sentences earn their place, though the terseness leaves room for a bit more operational structure without bloat.

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?

For a mutating deployment tool with four parameters and no annotations, the description is incomplete. It fails to explain the confirmation workflow, prerequisites, or relationship to app recovery lifecycle siblings, so an agent would struggle to invoke it correctly.

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?

Schema description coverage is 50%, with confirm and confirmation_token undocumented, and the description adds no meaning for any parameter. It doesn't clarify what confirmation_token is for, when confirm must be true, or how they relate to deploying the recovery action.

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 states a specific action ('Deploy') and resource ('app recovery action') targeted at users, which clearly differentiates it from deploy_app and from create/cancel/list siblings. It does not explicitly describe what deployment entails or how it differs from create_app_recovery, so it stops short of a fully differentiating statement.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus siblings like create_app_recovery, add_app_recovery_targeting, or cancel_app_recovery. The only contextual note, 'Disabled in read-only mode,' is a constraint rather than usage guidance.

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