Google Play MCP

delete_base_plan

Delete a draft subscription base plan that has never been activated. This irreversible action removes unused base plans from Google Play.

Instructions

Delete a base plan. Only draft base plans (never activated) can be deleted. Irreversible.

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>",
      "productId": "<productId>",
      "basePlanId": "<basePlanId>"
    },
    "name": "delete_base_plan"
  }
}

Input Schema

Name	Required	Description
`productId`	Yes	Subscription product id
`basePlanId`	Yes
`packageName`	Yes	Application id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden: it correctly discloses that the operation is irreversible and gated on draft status, which is the most important safety fact. It says nothing about required permissions, error behavior when a plan has been activated, or whether the parent package/product must be in an editable state, leaving real gaps for a destructive tool.

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?

Three short sentences, each carrying a distinct fact: action, precondition, irreversibility. The destructive warning is front-loaded and nothing is redundant.

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?

For a three-parameter destructive tool with no annotations and no output schema, the definition covers the essentials: what it removes, the eligibility gate, and that it cannot be undone. Only the undefined basePlanId parameter and unstated failure modes keep it from full marks.

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 coverage is 67% – two of three parameters are documented, basePlanId is not. The description adds no parameter meaning at all (no id format, no hint about where basePlanId comes from), so it neither compensates for the coverage gap nor reinforces the documented fields.

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 verb and resource ('Delete a base plan') and immediately bounds the scope to draft, never-activated plans. It does not name a contrasting sibling such as deactivate_base_plan, but the 'never activated' qualifier implicitly separates it from lifecycle tools for live plans.

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?

It gives a clear eligibility condition for use ('Only draft base plans (never activated) can be deleted'), which tells an agent when the call will succeed. It stops short of naming the alternative for active plans, so the exclusions are conditional rather than routed to a specific sibling.

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

Deploy Server