Skip to main content
Glama

update_listing

Update app store listing text for a specific locale, creating the listing if it doesn't exist. Validate changes first using the validate_only flag to prevent errors.

Instructions

Update the store listing text for one locale. Only the fields you pass are changed, so you can edit just the title without touching the description. Creates the listing if that locale does not exist yet. Google's limits: title 30 characters, short description 80, full description 4000. Use validate_only first to check the change without committing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoApp name shown on the store, max 30 characters
videoNoYouTube URL of the promo video. Pass an empty string to remove it.
languageYesBCP-47 language tag of the listing, e.g. 'en-US' or 'de-DE'
package_nameNoApp package name, e.g. 'com.acme.app' (defaults to GOOGLE_PLAY_PACKAGE_NAME)
validate_onlyNoDry run: validate the change and discard the edit instead of committing it
full_descriptionNoFull store description, max 4000 characters
short_descriptionNoTagline shown above the fold, max 80 characters
changes_not_sent_for_reviewNoCommit without sending the changes for review (only for apps where changes are reviewed separately)
Install Server

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 key behaviors: partial updates (only passed fields change), automatic creation for missing locales, Google's character limits, and the validate_only dry-run option. It does not cover review-skipping behavior or auth/rate limits, but covers the essential operational traits.

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?

Five short, information-dense sentences front-load the purpose and then add behavioral details, limits, and a usage tip. No filler or redundancy.

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 an 8-parameter tool with no output schema, the description covers purpose, update semantics, creation, limits, and validation flow. It omits some details like changes_not_sent_for_review semantics, but the schema covers those. Overall, it's complete enough for effective selection and invocation.

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. The description adds meaningful context about partial updates (only passed fields are changed) and reiterates character limits, which clarifies how parameters interact. However, individual parameter descriptions already exist in the schema, so added value is moderate.

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 the tool updates store listing text for one locale, explicitly differentiating from read-only siblings like list_listings and get_listing. It also clarifies partial update scope and creation-if-missing behavior, making the purpose unmistakable.

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?

It provides clear context for when to use (updating listing text) and a specific best practice to use validate_only first. It does not explicitly name alternatives like update_app_details, but the 'one locale' and 'listing text' framing implies the scope. Thus clear context, but no explicit exclusions.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OrellBuehler/play-console-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server