Skip to main content
Glama

google_update_listing

Update the store listing for a specific language in Google Play Console. Provide package name, edit ID, and language code to modify title, short description, or full description.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageNameYesAndroid package name
editIdYesEdit ID
languageYesLanguage code (e.g. ko-KR, en-US)
titleNoApp title (max 30 chars)
shortDescriptionNoShort description (max 80 chars)
fullDescriptionNoFull description (max 4000 chars)
Behavior2/5

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

No annotations are present, so the description carries full burden. It only states 'Update store listing' but does not disclose side effects, partial update behavior, or requirement to commit, leaving significant behavioral gaps.

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?

The description is a single concise sentence with no wasted words. It is front-loaded with the verb. However, it could be slightly more informative without becoming verbose.

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?

Given the complexity (6 parameters, no annotations, no output schema), the description is incomplete. It does not explain the response, mention edit state requirements, or provide necessary context for correct usage.

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?

Schema description coverage is 100%, so baseline is 3. The description mentions 'title, descriptions' which matches three parameters but adds no additional meaning beyond what the schema already provides.

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 clearly states the action (update), resource (store listing), and scope (for a specific language, title, descriptions). It distinguishes from sibling tools like google_get_listing and google_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 Guidelines2/5

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

No usage guidelines are provided. The description does not indicate when to use this tool vs alternatives like google_update_details, nor does it mention prerequisites such as needing an editId from google_create_edit.

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

Install Server

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/mikusnuz/app-publish-mcp'

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