Skip to main content
Glama
Sign In
Google Play Console MCP

Google Play Console MCP

by abd3lraouf-studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete All Listings

delete_all_listings

Delete every localized store listing for an app in a single commit. Preview the destructive change, then confirm to permanently remove all locale-specific listing text.

Instructions

Delete every localized store listing for an app.

Destructive: the listing text for all locales is removed in one commit and the API offers no undo. Two-step: preview, then confirm.

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": {
      "package_name": "<package_name>"
    },
    "name": "delete_all_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet True only after the user approved the preview
package_nameYesApp package name (e.g., com.example.myapp)
confirmation_tokenNoThe token from that preview; never invent one

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden. It explicitly warns that the operation is destructive, removes all locales in one commit, and offers no undo, and it reveals the two-step preview/confirm behavior. It does not mention permissions, but the core irreversible side effect is clearly communicated.

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?

Three short lines, with the operation stated first and the most important safety warning immediately after. Every sentence adds meaningful information and nothing is redundant with the schema.

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 destructive bulk tool, the description covers scope, irreversibility, and the required confirmation workflow. An output schema exists, so return details are not necessary. A brief pointer to the singular delete_listing alternative would make it fully complete.

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 documents confirm and confirmation_token. The description adds the two-step preview/confirm workflow context, which clarifies the relationship between those parameters, but most parameter-level meaning already comes from the schema.

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?

States a specific verb and resource: deletes every localized store listing for an app, not just one listing or a single locale. This distinguishes it clearly from the singular sibling delete_listing and from update_listing.

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

Usage Guidelines4/5

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

The description provides clear context: this is the bulk, all-locales deletion operation and it must be preceded by a preview step and followed by explicit confirmation via the confirm field. It does not explicitly name alternative tools for single-listing deletion, so it stops just short of a 5.

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