Google Play Console MCP

Overview Schema Source Related Servers Discussions Admin

Update Expansion File

update_expansion_file

Assign a version's expansion file reference to another version's file, replacing the current OBB resource for that app version.

Instructions

Set a version's OBB reference, replacing the whole resource.

Same effect as patch_expansion_file but with the API's update (full replace) semantics.

Input Schema

TableJSON Schema

Name	Required	Description
`package_name`	Yes	App package name (e.g., com.example.myapp)
`version_code`	Yes	Version code to attach the reference to
`references_version`	Yes	Version code whose expansion file to reference
`expansion_file_type`	Yes	"main" or "patch"

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Aug 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

There are no annotations, so the description carries the burden of behavioral disclosure. It clearly states that the operation replaces the whole resource, which is a key destructive trait. It does not go into permissions or side effects, but the core behavior is transparent.

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 concise sentences with no filler. The main action is front-loaded, and the sibling differentiation is delivered in a single efficient second sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a simple four-parameter schema, full schema coverage, and an output schema present, the description provides the essential selection context: what the tool does, that it is destructive/full-replace, and how it relates to patch_expansion_file. Nothing critical is missing.

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% parameter description coverage, so the schema already documents each parameter. The description does not add parameter-specific semantics beyond the overall 'full replace' behavior, meeting the baseline of 3.

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 uses a specific verb-resource pair ('Set a version's OBB reference') and then differentiates itself from patch_expansion_file by highlighting full-replace update semantics. This makes the tool's purpose unambiguous and clearly distinguishes it from the closely related sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly names the alternative patch_expansion_file and contrasts the API update (full replace) semantics with patch semantics. This tells the agent to choose this tool when full replacement is intended and implies using patch_expansion_file for partial updates.

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

Deploy Server