google-play-developer-mcp

images_delete_all

Delete every image of a specified type (e.g., screenshots, feature graphic) for a particular locale in a Google Play app edit.

Instructions

Delete every image of a given type in one locale.

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

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by `edits_insert` — required for all edits.* writes
`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

B3.2/5.0

Behavior2/5

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

The description omits critical behavioral details such as irreversibility, dependency on an active edit session, or authorization requirements. Given no annotations, the description should fully disclose these traits.

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?

The description is a single concise sentence with no redundancy, fitting the tool's straightforward purpose.

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?

The description lacks information about output, side effects, and safe usage. For a destructive bulk operation with 4 required parameters and no output schema, more context is needed.

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 75% (3 of 4 parameters described). The description adds minimal value by linking imageType and language, but does not compensate for the missing imageType description.

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 states the verb 'Delete', the resource 'every image of a given type', and the scope 'in one locale'. It effectively distinguishes from sibling tools like images_delete (single image) and images_upload.

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 is provided on when to use this tool versus alternatives such as images_delete. There is no mention of prerequisites, conditions, or when not to use it.

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

Deploy Server