google-play-developer-mcp

subscriptions_delete

Delete a subscription with no active base plans or offers by providing the package name and product ID.

Instructions

Delete a subscription. Only works on subscriptions with no active base plans/offers.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the precondition but does not disclose other behavioral traits such as auth requirements, rate limits, irreversibility of deletion, or error scenarios. More details are needed for safe invocation.

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 consists of two concise sentences: the first states the core function, the second adds a critical condition. No extraneous words. Well-structured for quick understanding.

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?

With no output schema and limited annotations, the description omits return values, side effects, and error handling. For a deletion tool with several siblings, more context (e.g., whether deletion is reversible, what happens to base plans) is necessary for an agent to use 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?

The description adds no information about the parameters (packageName, productId, latencyTolerance). Schema coverage is 67% but the missing parameter (latencyTolerance) has no schema description. The description fails to clarify or constrain this parameter's role, leaving ambiguity.

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 verb 'delete' and resource 'subscription', and adds a specific condition ('only works on subscriptions with no active base plans/offers'), which distinguishes it from related tools like subscriptions_archive.

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 description provides a clear precondition for when to use the tool (subscriptions with no active base plans/offers). However, it does not mention when not to use it or suggest alternatives like subscriptions_archive or subscriptions_batch_update.

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

Deploy Server