google-cloud-console-mcp

Delete all images of a type

play_delete_all_images

Delete all images in a Google Play store listing image slot for a specific language, such as clearing every phone screenshot, by providing package, edit, language, and image type.

Instructions

Deletes every image in a given image slot for a language (e.g. clear all phoneScreenshots).

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>",
      "editId": "<editId>",
      "language": "<language>",
      "imageType": "<imageType>"
    },
    "name": "play_delete_all_images"
  }
}

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by play_create_edit
`language`	Yes	BCP-47 language code as used by Play Console, e.g. "en-US", "tr-TR"
`imageType`	Yes	Which image slot in the store listing to operate on
`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

B3.3/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 does disclose the destructive scope ('every image in a given image slot'), which is genuinely useful, but says nothing about irreversibility, whether the deletion must be committed via play_commit_edit to take effect, or what happens to existing images.

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?

One sentence, front-loaded with the verb and scope, with a parenthetical example that earns its place by clarifying the target slot.

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

Completeness3/5

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

For a destructive, four-required-parameter mutation with no annotations and no output schema, the description omits the edit-lifecycle context (editId originates from play_create_edit and the deletion likely needs to be committed). It is adequate but leaves an agent to piece together prerequisites from sibling tools.

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 description coverage is 100%, so all four parameters are already documented, and imageType carries an enum. The description adds only a loose gloss ('image slot') on imageType, which the schema already states more precisely. Baseline 3 applies.

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?

States a specific verb (Deletes) and resource (every image in a given image slot for a language), with a concrete example ('clear all phoneScreenshots'). This distinguishes it well from the singular sibling play_delete_image, though it never names that sibling explicitly.

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 example 'clear all phoneScreenshots' implies the bulk-clear use case, but there is no explicit when-to-use guidance and no mention of when to prefer play_delete_image (single) or that this operates within an edit session. Usage must be inferred.

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

Deploy Server