app-publish-mcp

google_update_listing

Updates a Google Play store listing for a specific language and edit, setting the app title, short and full descriptions, and promotional YouTube video.

Instructions

Update store listing for a specific language (title, descriptions, promo video)

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

Input Schema

Name	Required	Description
`title`	No	App title (max 30 chars)
`video`	No	URL of a promotional YouTube video for the app
`editId`	Yes	Edit ID
`language`	Yes	Language code (e.g. ko-KR, en-US)
`packageName`	Yes	Android package name
`fullDescription`	No	Full description (max 4000 chars)
`shortDescription`	No	Short description (max 80 chars)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.7.0Oct 25, 2026

addedInput schema / properties / video

Added value: +{
+  "description": "URL of a promotional YouTube video for the app",
+  "type": "string"
+}

First observedv0.3.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a mutation tool. It does not state whether omitted fields are preserved or cleared, whether the change is staged in an edit and requires commit, or what permissions/validation constraints apply (e.g. character limits), so real behavioral risk remains undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the verb, resource, and language scoping all arrive immediately. It is arguably too terse for a mutation tool, but nothing is wasted.

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

Completeness2/5

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

Seven parameters, three required, no annotations, and no output schema: the description should at minimum signal the edit-staging workflow and partial-update semantics. As written, an agent could invoke it without knowing the change must be committed, which is a significant completeness gap for a write operation.

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?

The parenthetical '(title, descriptions, promo video)' loosely maps to the schema fields and adds a small amount of grouping value. However, schema description coverage is 100% with per-field constraints already documented, so the description adds no syntax, format, or requirement details beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Update') and resource ('store listing') plus the scoping dimension ('for a specific language'), which clearly separates it from google_get_listing, google_list_listings, and google_delete_listing. It is also implicitly distinct from google_update_details, though it never names that sibling or explains the boundary between 'listing' and 'details'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus google_update_details, nor any mention of the prerequisite edit flow (goog_create_edit / commit_edit) despite editId being required. The agent must infer the entire call sequence from the schema alone.

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

Deploy Server