Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

restore_listing

Restores listing text and optional app details from a snapshot file in one atomic edit, leaving newer languages untouched. Use dry-run to preview and validate changes without publishing.

Instructions

Restore listing text (and optionally app details) from a snapshot_listing file, in one atomic edit. Languages added since the snapshot are left alone. Images are not restored. Set dryRun:true to see what would change and 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": {
      "file": "<file>"
    },
    "name": "restore_listing"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesPath returned by snapshot_listing
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.
languagesNoRestore only these languages (default: all in the snapshot)
packageNameNoDefaults to the snapshot's packageName; pass to double-check the target
includeDetailsNoAlso restore contact email/phone/website + defaultLanguage (default false)
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

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses the important traits: an atomic edit, selective language scope, images excluded, and a non-publishing preview mode. It stops short of stating whether a call without editId commits/publishes immediately, which is the key remaining behavioral question for a mutation.

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?

Four short sentences, front-loaded with the core action and scope, then exclusions, then the safe-preview path. No redundant restatement of the name or title.

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 7-parameter mutation with no annotations and no output schema, the description covers scope, exclusions, and preview semantics well. It leaves the publish-versus-edit outcome ambiguous when editId is omitted, and says nothing about the failure modes of restoring a stale snapshot.

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 the baseline is 3; the description earns above that by clarifying languages semantics ('languages added since the snapshot are left alone') and framing includeDetails as 'optionally app details', which neither parameter's schema text states as plainly.

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 ('Restore listing text ... from a snapshot_listing file') and immediately bounds the operation with two exclusions: images are not restored and languages added after the snapshot are left alone. An agent can distinguish this from update_listing or snapshot_listing without opening either schema.

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?

Gives a clear triggering context (restoring from a snapshot file), a validation path (dryRun:true to preview and validate without publishing), and the schema documents the batching alternative via editId. It does not explicitly contrast against update_listing for partial restores, so it stops short of a full when/when-not statement.

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