google-cloud-console-mcp

Create Play Console edit

play_create_edit

Start an edit transaction for a Play Console app to upload bundles or APKs and modify tracks, listings, or details. Returns an editId for other play_* tools, finalized via play_commit_edit.

Instructions

Starts a new edit transaction for a Play Console app. Required before uploading a new bundle/APK or changing tracks, listings, or details. Returns an editId to pass to the other play_* tools, and must be finished with play_commit_edit (or discarded with play_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": "play_create_edit"
  }
}

Input Schema

Name	Required	Description	Default
`packageName`	Yes	Play Console package name, e.g. "com.example.app"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that this opens a stateful transaction, that the returned editId must be threaded into other play_* tools, and that the transaction must be explicitly finished or discarded. It stops short of stating auth/scope requirements or whether edits expire, which is the only remaining behavioral gap.

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 sentences, each earning its place: purpose, precondition, and return/lifecycle. The most decision-relevant information (the transaction requirement) is front-loaded.

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?

There is no output schema, so the description compensates by explaining the return value (editId) and how it is consumed downstream. For a one-parameter tool with a clear lifecycle, nothing an agent needs to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% for the single packageName parameter, and the schema already supplies the format example, so the baseline of 3 applies. The description adds no syntax or constraint detail beyond the schema.

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?

States a specific verb and resource ('Starts a new edit transaction for a Play Console app') and immediately scopes it against the sibling edit tools by naming the commit/discard lifecycle. An agent can distinguish this from play_get_edit, play_validate_edit, and play_commit_edit without opening a schema.

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?

Explicitly states the prerequisite condition: required before uploading a bundle/APK or changing tracks, listings, or details. It also names the two terminating alternatives (play_commit_edit, play_delete_edit), so the when-to-use and what-to-do-next paths are both spelled out.

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

Deploy Server