google-play-developer-mcp

apks_add_externally_hosted

Instructions

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

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by `edits_insert` — required for all edits.* writes
`packageName`	Yes	Android application package name, e.g. com.example.app
`externallyHostedApk`	Yes	ExternallyHostedApk resource body

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jun 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It describes registration but lacks details on what happens on success, if the APK already exists, or the required edit context. It does mention enterprise-only and allowlist, which are access constraints.

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?

A single 12-word sentence that is front-loaded with the verb and resource. No wasted words; every part earns its place.

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 is missing behavioral context (e.g., return value, what constitutes a successful registration) and does not explain the nested externallyHostedApk structure beyond what the schema provides.

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%, so the baseline is 3. The description adds minimal meaning beyond the schema: 'register' implies the externallyHostedApk parameter contains the APK details, but the schema already describes it as a resource body.

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 action ('Register') and the resource ('an APK that is hosted outside Google Play'). It also adds critical constraints ('enterprise-only, requires allowlist'), distinguishing it from sibling tools like apks_upload.

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 provides explicit context: the tool is only for enterprise accounts with an allowlist. However, it does not name alternative tools (e.g., apks_upload for internally hosted APKs) or state when not to use this tool.

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

Deploy Server