app-publish-mcp

google_get_details

Retrieve app details including default language, contact email, phone, and website from Google Play Console using the Android package name and edit ID.

Instructions

Get app details (default language, contact email/phone/website)

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

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.6/5.0

Behavior3/5

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

No annotations are present, so the description carries the transparency burden. It correctly implies a read-only operation ('Get'), but does not disclose potential side effects, authentication requirements, or rate limits. The listed fields give some output context.

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 concise sentence that front-loads the purpose and specific details. No unnecessary words or repetition.

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?

Given the lack of an output schema, the description compensates by listing three specific fields returned (default language, contact email, phone, website). This provides useful context for the agent, though the full output may include more fields.

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?

The input schema has 100% coverage, with descriptions for both packageName and editId. The description does not add any additional parameter-level information beyond what the schema 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 verb 'Get' and the resource 'app details', listing specific fields like default language, contact email/phone/website. This distinguishes it from sibling tools like google_get_listing or google_get_iap, making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives. The description merely states what it does, without exclusions or context regarding other 'get' tools for Google Play.

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

Deploy Server