Skip to main content
Glama
devinwang

google-play-developer-mcp

by devinwang

listings_delete_all

Delete all locale listings for a given edit ID and Android app package. This action is irreversible within the edit.

Instructions

Delete ALL locale listings in this edit. Irreversible within the edit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid application package name, e.g. com.example.app
editIdYesEdit id returned by `edits_insert` — required for all edits.* writes
Behavior5/5

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

Explicitly warns 'Irreversible within the edit', disclosing a critical behavioral trait (destructive, no undo). This is valuable as no annotations are provided.

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 sentences, direct and to the point, with no redundant information. The key action and consequence are front-loaded.

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

Completeness5/5

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

A simple bulk-delete tool; the description covers the operation, scope (all locale listings), and irreversibility. No output schema exists, so return value explanation is unnecessary.

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?

Both parameters are fully described in the input schema (100% coverage). The description adds no additional detail beyond the schema, but the schema already provides sufficient meaning.

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?

Description explicitly states 'Delete ALL locale listings in this edit', clearly identifying the action, scope, and target resource. Distinguished from likely sibling 'listings_delete' which would delete a single 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?

Clearly implies usage when all locale listings need removal. Does not explicitly state when not to use or compare to siblings, but the context of 'all' vs individual deletion is understood.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/devinwang/google-play-developer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server