Google Play MCP

delete_subscription_offer

Permanently deletes a draft subscription offer from a Google Play subscription base plan; only never-activated offers can be removed, and the action is irreversible.

Instructions

Delete a subscription offer. Only draft offers (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>",
      "offerId": "<offerId>"
    },
    "name": "delete_subscription_offer"
  }
}

Input Schema

Name	Required	Description
`offerId`	Yes
`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.7/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose the two traits that matter most: the operation is irreversible and it is restricted to never-activated drafts. It omits permission/auth requirements, cascade effects on regional or price configuration, and whether the call must occur inside an edit transaction.

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, front-loaded with the action, followed by the eligibility constraint and the risk warning. No filler, no restatement of the name.

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-required-parameter destructive tool with no annotations and no output schema, the description covers purpose, precondition, and irreversibility but leaves two bare parameters unexplained and says nothing about the edit/commit workflow implied by sibling tools such as commit_edit and delete_edit. Adequate but with clear gaps for a mutation of this kind.

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 only 50% (productId and packageName documented; offerId and basePlanId bare), and the description adds no parameter meaning at all. It neither explains how offerId relates to basePlanId nor gives format guidance, so the undocumented half of the schema remains unexplained in both places.

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 opens with a specific verb+resource: 'Delete a subscription offer.' The resource name distinguishes it from sibling delete_subscription and delete_base_plan by object type. It does not explicitly say how it differs from those siblings, but the resource scope is unambiguous.

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?

'Only draft offers (never activated) can be deleted' is an explicit eligibility condition that rules out a large class of candidates. However, it does not route the agent to an alternative (e.g., deactivate_subscription_offer) for non-draft offers, so the when-not is stated without naming the fallback.

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

Deploy Server