Google Play MCP

snapshot_listing

Saves a timestamped JSON snapshot of an app's editable listing metadata, including titles and descriptions per language, so bulk edits can be reverted later with restore_listing.

Instructions

Save a timestamped JSON snapshot of an app's editable TEXT metadata — app details plus title / short & full description / video for every language — so bulk edits can be reverted with restore_listing. includeImages:true also records each image's id, hashes and preview URL (a record only; image files are not downloaded). Returns the snapshot file path. Read-only on Google Play.

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>"
    },
    "name": "snapshot_listing"
  }
}

Input Schema

Name	Required	Description
`label`	No	Optional label added to the filename
`packageName`	Yes	Application id (package name), e.g. com.example.app
`includeImages`	No	Also record image ids/hashes/urls per language and type (slower)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

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 discloses important behavior: it writes a local timestamped JSON file, returns the file path, is read-only on Google Play, and includeImages only records image metadata rather than downloading files. It does not cover storage location details or overwrite behavior, but the core behavioral profile is clear.

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?

The description is front-loaded with the core action and scope, then adds includeImages, return value, and read-only behavior in compact follow-up sentences. Dense wording is justified because every clause adds operational detail without repetition.

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 snapshot tool without an output schema, the description provides enough context to call it correctly: what metadata is captured, what includeImages changes, that image files are not downloaded, that it returns a file path, and that it is read-only on Google Play. Minor operational details such as overwrite/collision behavior are missing but not central.

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 schema already explains all three parameters. The description still adds meaningful meaning for includeImages by clarifying that it records image ids, hashes, and preview URLs but does not download image files. It does not add much for label beyond 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?

The description states a specific verb and resource: saving a timestamped JSON snapshot of an app's editable text metadata. It scopes the contents precisely, including app details plus title, short/full descriptions, and video per language, and mentions includeImages behavior. It also distinguishes the tool from restore_listing by framing snapshots as revert targets.

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 clearly implies the use case: snapshot before bulk edits so they can be reverted with restore_listing. It names the counterpart restore tool explicitly but does not spell out when not to use it or compare it directly against get_listing/update_listing alternatives.

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

Deploy Server