Skip to main content
Glama
abd3lraouf-studios

Google Play Console MCP

Clone Listing To Locale

clone_listing_to_locale

Copy a store listing's title, description, and video from one locale to another without duplicating images. Leaves non-empty target listings untouched unless overwrite is enabled.

Instructions

Copy a store listing's TEXT from one locale to another.

Copies title, descriptions and video. Images are not cloned — that means downloading and re-uploading every asset, a different operation with different failure modes.

A locale that already has a listing is left alone unless overwrite is set, so this cannot silently replace translated copy with the source language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet True only after the user approved the preview
overwriteNoReplace an existing listing in the target locale
package_nameYesApp package name (e.g., com.example.myapp)
source_languageYesLocale to copy from (e.g., en-US)
target_languageYesLocale to copy to (e.g., en-GB)
confirmation_tokenNoThe token from that preview; never invent one

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/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 burden and does disclose important behaviors: images are not cloned, existing target-locale listings are preserved unless overwrite is true, and it cannot silently replace translated copy. It does not mention the preview/confirmation workflow, but the schema begins to cover that.

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?

Roughly 70 words in three short paragraphs, with the purpose front-loaded in the first sentence. Every sentence contributes a distinct fact: scope, field list, image exclusion, and overwrite behavior.

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?

Given the rich input schema, full parameter descriptions, and an output schema, the description covers the key selection and safety facts without needing to repeat return values. A small gap is that the confirmation-token/preview flow is only implied via the schema and not tied into the description's narrative.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all six parameters are described there. The description adds real semantic value by defining what 'copy' includes, explicitly excluding images, and clarifying that overwrite is what controls replacement of an existing target listing.

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?

The description opens with a specific verb and resource: 'Copy a store listing's TEXT from one locale to another.' It then enumerates exactly what is copied (title, descriptions, video) and explicitly excludes images, cleanly distinguishing this tool from broader listing-related tools.

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 gives a clear when-not and alternative: images are not cloned, and cloning them would require a different download/re-upload operation with different failure modes. It also explains when overwrite matters ('left alone unless overwrite is set'), though it does not name a specific sibling tool as an alternative.

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