Google Play MCP

get_app_details

Read an app's default language and public contact email, phone, and website by package name, optionally from an open edit to view uncommitted changes.

Instructions

Read app-level details: defaultLanguage and the public contact email / phone / website. 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>"
    },
    "name": "get_app_details"
  }
}

Input Schema

Name	Required	Description	Default
`editId`	No	Optional: read from this open edit (to see uncommitted changes). Without it a temporary edit is opened and deleted.
`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

A3.5/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does declare 'Read-only,' which is the most important safety trait. However, it omits the non-obvious side effect that calling without editId opens and deletes a temporary edit (that fact lives only in the schema), and says nothing about permissions or rate limits.

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?

Two short sentences, front-loaded with the returned fields and closed with the read-only marker; no filler. The terse 'Read-only.' fragment is functional rather than wasteful.

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?

With no output schema, the description usefully enumerates what comes back, which is the main thing an agent needs. The remaining gap is the undisclosed temp-edit side effect of omitting editId and the absence of any alternative-tool routing, both of which are minor for a two-parameter read tool.

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%, including a clear explanation of editId's temporary-edit behavior, so the schema does the heavy lifting. The description adds no parameter meaning of its own and does not connect the listed fields (e.g. contact details) to the optional edit context.

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?

The description gives a specific verb ('Read') and a specific resource ('app-level details') and enumerates the exact fields returned (defaultLanguage, contact email/phone/website), which lets an agent distinguish it from update_app_details and from listing/track getters. It stops short of naming any sibling explicitly, so the differentiation is inferred from scope 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 Guidelines3/5

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

Usage is only implied: it is the read counterpart to update_app_details, and the field list hints the tool is for contact/localization metadata rather than listings, tracks, or reviews. There is no explicit when-to-use or when-not guidance and no pointer to an alternative for adjacent data.

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

Deploy Server