google-play-developer-mcp

subscriptions_create

Create a subscription in Google Play by providing the package name, product ID, and subscription resource details.

Instructions

Create a subscription.

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

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
`subscription`	Yes	Subscription resource body
`regionsVersion`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

C2.5/5.0

Behavior2/5

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

The description gives no behavioral details beyond 'create a subscription'. No mention of side effects, required permissions, or response. With no annotations, the description fails to disclose essential behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While extremely concise, the description is too sparse for a tool with 4 parameters and a nested object. It fails to convey necessary information, making it under-specified rather than efficiently concise.

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?

Given no output schema, no annotations, and a complex input schema, the description is grossly incomplete. It does not explain what happens when a subscription is created, required permissions, or the response format.

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 value to the already provided parameter descriptions. The nested 'subscription' object is not elaborated, and the 'regionsVersion' parameter has no schema description. The description does not compensate for schema gaps.

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 it creates a subscription, clearly distinguishing it from sibling tools like subscriptions_delete or subscriptions_update. However, it lacks specificity about the type of subscription or any additional context.

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?

No guidance on when to use this tool versus alternatives such as subscriptions_batch_create or subscriptions_archive. The description does not mention prerequisites or context.

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

Deploy Server