Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

update_listing

Update Google Play store listing title, short/full description, or promo video for one language, creating it if missing. Preview and validate changes with dryRun before publishing.

Instructions

Update the store listing TITLE, SHORT DESCRIPTION, FULL DESCRIPTION or promo video for one language (creates the language if it doesn't exist yet). Only include the fields you want to change. Opens an edit, applies, validates and commits in one call. Set dryRun:true to preview the diff (old→new + length checks) and have Google validate it without publishing anything.

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

Input Schema

NameRequiredDescriptionDefault
titleNoApp title (max 30 chars)
videoNoYouTube URL of the promo video
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.
languageYesBCP-47 language tag, e.g. en-US, de-DE
packageNameYesApplication id (package name), e.g. com.example.app
fullDescriptionNoFull description (max 4000 chars)
shortDescriptionNoShort description (max 80 chars)
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 does well: it discloses the implicit side effect of creating the language if absent, and that one call opens an edit, applies, validates and commits. It stops short of stating what happens on validation failure (rollback or partial write) and doesn't mention the editId non-committing batch mode that the schema documents.

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 tight sentences, front-loaded with what is updatable, then the mutation flow, then the safety valve. Parenthetical asides carry genuine information (language creation, diff content) rather than filler.

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 9-parameter mutation tool with no annotations and no output schema, the description covers the fields, the write lifecycle, and the dry-run escape hatch. The remaining gap is return/error behavior and the editId batching mode, though the latter is fully documented in the schema.

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 baseline is 3, and the description adds real meaning on top: language is created when missing and dryRun is framed as an old→new diff with length checks. The editId batch path is left entirely to the schema, so it isn't a full-semantics win.

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 (update the store listing) and enumerates the exact updatable fields — title, short description, full description, promo video — plus the unit of operation (one language). The mention of language-scoped updates and commit behavior makes it clearly distinct from sibling readers/writers like get_listing or delete_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?

Gives clear conditional guidance: 'Only include the fields you want to change' for partial updates and 'Set dryRun:true to preview' for safe validation. What's missing is routing against neighboring writers such as update_app_details — the description never explains when to use this listing tool versus the app-details tool.

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