Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_all_images

Delete every image of a specified type for one store listing language, with a dry-run option to validate changes without publishing.

Instructions

Delete ALL images of one type for one language. Set dryRun:true to validate without publishing.

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

Input Schema

NameRequiredDescriptionDefault
dryRunNoPreview only: open a temporary edit, apply, validate, then delete it. Nothing is published (default false). Ignored when editId is set.
editIdNoOptional: an open edit from insert_edit. The change is applied inside that edit and NOT committed — batch several changes, then call commit_edit.
languageYesBCP-47 language tag, e.g. en-US, de-DE
imageTypeYes
packageNameYesApplication id (package name), e.g. com.example.app
changesNotSentForReviewNoCommit option: keep the changes out of review until sent from Play Console. Google requires this for some apps and rejects it for others — set it only if a commit error asks for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'Delete ALL' plus a dryRun preview path does convey that this is a bulk destructive operation with a safe validation mode, but it never states irreversibility, permission requirements, or what happens to existing images. The dryRun sentence largely restates the schema's own dryRun property description.

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?

Two short sentences with the destructive scope front-loaded and no filler. The second sentence duplicates schema content rather than adding new information, which keeps it just short of a 5.

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 6-parameter destructive tool with no annotations and no output schema, the description covers purpose and the safe-preview path but omits reversibility, permissions, and confirmation that only images of the given type/language are touched. The schema compensates on parameters, but the behavioral picture is thin.

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 83%, so the schema already documents dryRun, editId, language, imageType, packageName and changesNotSentForReview in detail. The description's dryRun mention adds no meaning beyond that, and the editId batching and changesNotSentForReview semantics are left entirely to the schema.

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 with scope: 'Delete ALL images of one type for one language.' The 'ALL' plus the type/language qualifiers make the blast radius clear and implicitly distinguish it from a single-image delete sibling, though 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?

It tells the agent how to preview safely ('Set dryRun:true to validate without publishing'), which is useful, but gives no guidance on when to choose this over delete_image or replace_images, nor any prerequisite or exclusion conditions.

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

Deploy Server

Other Tools