google-play-developer-mcp

subscription_base_plans_delete

Remove an inactive subscription base plan from Google Play by specifying package name, product SKU, and base plan ID.

Instructions

Delete a base plan (must be inactive).

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": "subscription_base_plans_delete"
  }
}

Input Schema

Name	Required	Description
`productId`	Yes	Product id / SKU — stable identifier you assign in Play Console
`basePlanId`	Yes
`packageName`	Yes	Android application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It only says 'delete', which implies a destructive action, but lacks details on permanence, required permissions, error conditions, or side effects on subscriptions.

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 sentence that directly states the action and key constraint. No extraneous words. Front-loaded with the verb and resource.

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 delete operation in a subscription management context, the description is too sparse. It does not address error scenarios (e.g., deleting an active plan), irreversibility, or required states. The lack of output schema and annotations exacerbates the gap.

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?

The schema already describes two of three parameters with 67% coverage. The description adds no further meaning beyond the schema, so it meets the baseline for minimal value added.

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 clearly states the action ('Delete') and resource ('base plan'), and includes a critical qualifier ('must be inactive'). This distinguishes it from sibling tools like subscription_base_plans_activate and subscription_base_plans_deactivate.

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 condition 'must be inactive' provides a clear prerequisite, implying the tool is only appropriate when the base plan is inactive. However, it does not explicitly mention when not to use it (e.g., active base plans) or suggest alternative tools like deactivate first.

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

Deploy Server