Google Play MCP

upload_internal_app_sharing

Uploads an .aab or .apk to Internal App Sharing and returns a download URL for authorized testers, enabling quick build distribution without edits, reviews, or tracks.

Instructions

Upload an .aab or .apk to Internal App Sharing and get a download URL for authorized testers. No edit, no review, no track — the fastest way to hand someone a build.

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>",
      "filePath": "<filePath>"
    },
    "name": "upload_internal_app_sharing"
  }
}

Input Schema

Name	Required	Description	Default
`filePath`	Yes	Absolute path to the .aab or .apk
`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

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the operation creates no edit, triggers no review, and touches no track, and that the result is a download URL for authorized testers. It omits permission/authentication requirements for the uploader, size limits, and whether re-uploading the same package replaces the prior artifact.

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 action and result, followed by the differentiator. Every clause carries information; nothing is redundant.

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?

For a two-parameter upload tool with no output schema, the description covers purpose, side effects, and the return value (a download URL), which is enough to call it correctly. Missing only operational details such as auth prerequisites and artifact retention.

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 both parameters (filePath, packageName) are already fully documented in the schema. The description adds no format or constraint detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Upload an .aab or .apk to Internal App Sharing') and adds the outcome ('get a download URL for authorized testers'). The clause 'No edit, no review, no track' implicitly differentiates it from the standard upload_apk/upload_bundle flow, which goes through an edit and track.

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 fastest way to hand someone a build' gives a clear usage context, and 'no edit, no review, no track' tells the agent this is for quick tester handoff rather than a release pipeline. It stops short of explicitly naming upload_apk or upload_bundle as the alternatives for tracked/release uploads, so the exclusion is implied rather than stated.

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

Deploy Server