google-play-developer-mcp

images_delete

Delete a single app store image by specifying package name, edit ID, locale, image type, and image ID. Use this to remove unwanted screenshots or graphics from a Play listing.

Instructions

Delete a single image by id.

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": "images_delete"
  }
}

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by `edits_insert` — required for all edits.* writes
`imageId`	Yes
`language`	Yes	BCP-47 locale, e.g. en-US, fr-FR, zh-Hans
`imageType`	Yes
`packageName`	Yes	Android application package name, e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states the action without indicating deletion is irreversible, requires an edit context, or does not immediately commit.

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?

Single sentence with no wasted words. Adequately concise but could benefit from slightly more detail without becoming verbose.

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?

With 5 required parameters and no output schema or annotations, the description is incomplete. It fails to explain the edit workflow, that deletion is within an unpublished edit, or what the response indicates.

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?

The schema covers 60% of parameters with descriptions. The tool description adds no extra meaning to the parameters (e.g., that imageId is obtained from images_list or images_upload).

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?

The description clearly identifies the verb ('Delete'), resource ('image'), and scope ('single by id'), distinguishing it from sibling tools like images_delete_all which delete multiple images.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., images_delete_all for bulk, images_upload for adding). No mention of prerequisites like having an active edit or that this does not commit changes.

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

Deploy Server