google-cloud-console-mcp

Delete one store listing image

play_delete_image

Deletes a single uploaded Google Play store listing image by imageId, removing outdated screenshots, icons, or banners from an app edit.

Instructions

Deletes a single uploaded image by its imageId (from play_list_images).

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

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by play_create_edit
`imageId`	Yes
`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 says only that an image is deleted; it omits that the deletion is irreversible, that it occurs within an uncommitted edit (editId required), and that the edit must be committed to take effect.

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 with no filler; the highest-value information (verb, resource, key identifier, source tool) is stated immediately.

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 5-required-parameter mutation tool with no annotations and no output schema, the description covers the identifier source but not the edit-lifecycle context (create edit, commit) that is essential to invoking it correctly.

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 80% and editId, language, imageType and packageName are already documented in the schema. The description adds one useful hint — that imageId comes from play_list_images — but nothing about the enum or edit scoping. 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 and resource ('Deletes a single uploaded image') and the identifier used (imageId). The word 'single' implicitly contrasts with play_delete_all_images, but no sibling is named 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?

Points the agent at play_list_images as the source of imageId, which implies usage flow, but gives no explicit when/when-not guidance or prerequisites (e.g., an active edit must exist).

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

Deploy Server