app-publish-mcp

google_list_listings

Retrieve all localized store listings for an Android app using its package name and edit ID. Get a complete overview of listings across all languages to manage and review app store content.

Instructions

List all store listings (all languages) for an app

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

Input Schema

Name	Required	Description	Default
`editId`	Yes	Edit ID
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, and the description does not mention behavioral traits such as read-only nature, required prerequisites (e.g., an active edit), or pagination. The burden is entirely on the description, which is insufficient.

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 a single sentence with no unnecessary words. It conveys the essential purpose efficiently.

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

Completeness3/5

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

Given no output schema and no annotations, the description lacks context about the requirement for an edit ID and what a listing includes. It is moderately complete but leaves gaps for an AI agent.

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% with clear parameter names and descriptions. The description adds no extra meaning beyond what the schema already provides, so baseline score of 3 is appropriate.

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 specifies the action 'List', the resource 'store listings', and clarifies the scope 'all languages'. It clearly distinguishes from sibling tools like google_get_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?

The description implies listing all listings without filtering, but does not explicitly state when to use it versus alternatives like google_get_listing for a single listing. No usage exclusions are provided.

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

Deploy Server