app-publish-mcp

google_get_listing

Retrieve a Google Play store listing for your Android app by providing the package name, edit ID, and language code.

Instructions

Get store listing for a specific language

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_get_listing"
  }
}

Input Schema

Name	Required	Description
`editId`	Yes	Edit ID
`language`	Yes	Language code (e.g. ko-KR, en-US, ja-JP)
`packageName`	Yes	Android package name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only restates the tool name's implication of a read operation, without specifying permission requirements, error handling, or whether the listing is fetched from a cache or live. The description adds no value beyond the name.

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 sentence, concise and front-loaded. It is appropriately sized for a simple read operation, though it could be slightly more informative without being 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 no output schema or annotations, the description should elaborate on what the store listing contains or how it behaves (e.g., returns a localized listing or fields). The current description is too minimal for a complete understanding, lacking context about return value or potential failures.

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 coverage is 100%, with each parameter having a description. The tool description adds minimal extra meaning, only explicitly linking 'language' to the language parameter. This meets the baseline of 3 for high coverage.

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 verb 'Get', resource 'store listing', and scope 'for a specific language'. It distinguishes from sibling tools like 'google_list_listings' (list all) and 'google_update_listing' (update).

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

Usage Guidelines3/5

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

The description implicitly conveys usage: use when you need a single listing for a language. However, it provides no explicit guidance on when not to use it or alternatives, such as 'google_list_listings' for multiple languages.

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

Deploy Server