Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_listing

Delete a specific language's Google Play store listing while preserving the default language; use dryRun to validate without publishing.

Instructions

Delete one language's store listing (the default language cannot be deleted). 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>"
    },
    "name": "delete_listing"
  }
}

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
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

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the default language cannot be deleted and that dryRun validates without publishing. It does not state whether deletion is irreversible, whether restore_listing can undo it, or what permissions are required.

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?

Two short sentences, front-loaded with the action and its main constraint. Every sentence adds useful information, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter delete tool with rich schema descriptions but no annotations or output schema, the description covers the core action, the default-language restriction, and dry-run validation. It could be more complete by mentioning undo/restore behavior or the edit workflow, but the schema already documents the editId and changesNotSentForReview parameters.

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 100%, so the schema already explains all five parameters in detail. The description restates the dryRun behavior but adds no new meaning beyond the schema, which matches the baseline of 3 when the schema does the heavy lifting.

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?

The description uses a specific verb and resource: 'Delete one language's store listing.' It also states a key scope constraint: the default language cannot be deleted. It does not explicitly differentiate itself from siblings such as restore_listing or update_listing, so it stops short of a 5.

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?

Usage is implied by the action and by the instruction to set dryRun:true to validate without publishing. However, there is no explicit guidance on when to choose this tool versus alternatives like update_listing or restore_listing, and no when-not-to-use guidance beyond the default-language restriction.

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