Skip to main content
Glama
Sign In
google-play-developer-mcp

google-play-developer-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

subscription_base_plans_batch_migrate_prices

Batch migrate prices for up to 100 subscription base plans in one API call. Automate subscription price updates with Google Play Developer MCP.

Instructions

Migrate prices on up to 100 base plans in one call.

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

Input Schema

NameRequiredDescriptionDefault
requestsYes
productIdYesProduct id / SKU — stable identifier you assign in Play Console
packageNameYesAndroid application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3/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. It discloses the batch size limit but omits behavioral details such as whether this is a destructive mutation, error handling, partial failure behavior, or required base plan states. This is insufficient for a mutation 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?

A single, front-loaded sentence efficiently conveys the core action and scope. Every word earns its place; no filler or redundancy.

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?

The description is extremely terse given the tool's complexity: three required parameters including an array of objects, no output schema, and no annotations. It lacks guidance on request structure, response format, and practical usage (e.g., how to construct each request). This leaves the agent underinformed.

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 coverage is 67% (two of three parameters have schema descriptions). The description adds no parameter-level information. The 'requests' parameter, which has no schema description and is a complex array of objects, remains completely undocumented. The description fails to compensate for the coverage gap.

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 clearly states the action ('migrate prices') and the resource ('base plans'), with a specific batch size limit ('up to 100'). This distinguishes it from the singular sibling tool (subscription_base_plans_migrate_prices) implicitly through the batch emphasis.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies batch usage (multiple plans in one call) but does not explicitly compare with the singular alternative or state when to prefer one over the other. No exclusions or prerequisites are mentioned.

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

Deploy Server

Other Tools