Google Play MCP

insert_edit

Opens a Google Play edit for an app and returns its editId, enabling multiple changes to be batched before committing or deleting the edit.

Instructions

Open a new edit (Google Play's transaction) for an app and return its editId. Use this only to BATCH several changes: pass the editId to the mutation tools, then call commit_edit once. Most tools open, validate and commit their own edit automatically, so you rarely need this. Always finish with commit_edit or delete_edit.

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

Input Schema

Name	Required	Description	Default
`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

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the tool creates a server-side edit session, that the editId must be threaded into mutation tools, and that the session must be terminated via commit_edit or delete_edit. It doesn't say whether an edit expires or what happens if abandonned, which keeps it short of a 5.

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

Conciseness4/5

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

Front-loaded with purpose, then usage constraint, then flow, then cleanup rule. Every sentence earns its place; the 'most tools ... so you rarely need this' line is slightly redundant with the batching instruction but reinforces the main risk.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter session-creation tool with no output schema, the description covers the whole lifecycle: what is created, what is returned, how it is used downstream, and how it is ended. An agent has enough to call it correctly and to know it can usually skip it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the sole parameter is documented; the description adds meaning the schema cannot, namely that the returned editId is the handle passed to mutation tools. That is the useful semantic link between input and output.

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?

Specific verb and resource: opens a new edit for an app and returns its editId, with the Google Play transaction concept named. It is clearly distinguished from the sibling mutation tools that do their own edit handling.

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

Usage Guidelines5/5

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

Explicit when-to-use (only to batch several changes), explicit when-not (most tools open/validate/commit their own edit, so you rarely need this), and a concrete flow (pass editId to mutations, then commit_edit once). It also names the required cleanup paths, commit_edit or delete_edit.

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

Deploy Server