Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_image

Deletes a single Google Play store image by its image ID, with an optional dry-run preview to validate the removal without publishing.

Instructions

Delete one image by id (from list_images). 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>",
      "imageId": "<imageId>"
    },
    "name": "delete_image"
  }
}

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.
imageIdYes
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?

No annotations are supplied, so the description carries the full burden; it does disclose the meaningful dryRun preview semantics ('without publishing'), which is genuine behavioral information. It omits irreversibility of the delete, the fact that changes may be staged in an edit rather than applied immediately, and any permission requirements — significant gaps for a destructive mutation.

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, front-loaded sentences with the core action and its id source stated first and the dryRun tip second. No filler, though the parenthetical could be slightly tighter.

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 seven-parameter destructive tool with no annotations and no output schema, the description covers only the basic action and dryRun. It leaves the edit/commit lifecycle and the consequences of a non-dry-run delete unexplained, relying on the schema to fill those gaps.

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 71%, so the schema already explains dryRun, editId, language, packageName and changesNotSentForReview. The description only adds the source of imageId (list_images); it says nothing about editId, the enum of imageType, or the interaction between dryRun and editId that the schema flags.

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 cardinality: 'Delete one image by id', which implicitly distinguishes it from the sibling delete_all_images. The parenthetical '(from list_images)' tells the agent where the id originates, though it never names delete_all_images as the bulk alternative.

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?

Gives a concrete path for obtaining the imageId and a hint to use dryRun:true for validation, which is real when-to-use guidance. It does not say when to choose this over delete_all_images, nor what prerequisites (e.g. an open edit or commit) apply before deletion takes effect.

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