Google Play MCP

get_listing

Reads one language's Google Play store listing by package name and BCP-47 language tag, optionally from an open edit to check uncommitted changes; read-only.

Instructions

Read one language's store listing. Read-only.

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

Input Schema

Name	Required	Description
`editId`	No	Optional: read from this open edit (to see uncommitted changes). Without it a temporary edit is opened and deleted.
`language`	Yes	BCP-47 language tag, e.g. en-US, de-DE
`packageName`	Yes	Application id (package name), e.g. com.example.app

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the most important trait: this is a non-mutating read. It says nothing about permissions, whether an uncommitted edit is required, or what is returned, so the side effect of implicitly opening a temporary edit is only visible in the schema, not here.

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?

Two short sentences, front-loaded with the operation and resource, with zero filler. Nothing in the text is redundant or wasted.

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?

For a three-parameter read tool with no output schema and no annotations, the definition is minimally adequate: the schema fills in parameter detail, but the description leaves the return value and the edit-context behavior unaddressed. An agent can call it, but has to rely entirely on structured fields to do so correctly.

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 packageName, language, and editId are already fully documented in the input schema, including the temporary-edit fallback for editId. The description adds no parameter meaning beyond that, which is the baseline 3 case.

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?

"Read one language's store listing" gives a specific verb plus resource and scopes it to a single language, which separates it from update_listing/delete_listing by operation. It does not explicitly name a sibling or contrast with bulk_upsert_listings, so differentiation is inferred rather than stated.

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 when-to-use guidance and no mention of alternatives such as get_app_details or get_edit, nor any prerequisite about needing an edit context. The only hint is 'Read-only', which implies a retrieval operation but does not tell the agent when this tool is the right choice.

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

Deploy Server