Skip to main content
Glama
Sign In
Google Play MCP

Google Play MCP

by fil-technology
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

upload_image

Upload a PNG/JPEG app listing image for a language: screenshots are appended, while icon, feature graphic, and TV banner are replaced; use dryRun to validate without publishing.

Instructions

Upload one PNG/JPEG image (icon, featureGraphic, tvBanner or a screenshot) for a language. Screenshots are appended; icon / featureGraphic / tvBanner hold a single image and are replaced. filePath is a local file. Set dryRun:true to validate without publishing.

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>",
      "language": "<language>",
      "imageType": "<imageType>",
      "filePath": "<filePath>"
    },
    "name": "upload_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoPreview only: open a temporary edit, apply, validate, then delete it. Nothing is published (default false). Ignored when editId is set.
editIdNoOptional: an open edit from insert_edit. The change is applied inside that edit and NOT committed — batch several changes, then call commit_edit.
filePathYesAbsolute path to a local PNG or JPEG
languageYesBCP-47 language tag, e.g. en-US, de-DE
imageTypeYes
packageNameYesApplication id (package name), e.g. com.example.app
changesNotSentForReviewNoCommit option: keep the changes out of review until sent from Play Console. Google requires this for some apps and rejects it for others — set it only if a commit error asks for it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 full burden and does deliver the most important behavioral trait: screenshot types are appended while icon/featureGraphic/tvBanner are destructively replaced. It omits auth/permission requirements and does not mention the edit-scoped batching flow (editId) or changesNotSentForReview, which are only covered in the schema.

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?

Four short sentences, front-loaded with the verb and resource, then the append/replace distinction, then the filePath constraint, then the dryRun escape hatch. No filler and nothing buried.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the core semantics an agent needs to call it correctly. The main gap is the edit-based workflow (apply inside an open edit vs commit), which only surfaces in the schema and is important for avoiding unintended edits.

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 86%, so the schema already documents nearly every parameter including editId and the dryRun/editId interaction. The description adds only marginal meaning — 'filePath is a local file' and the plain-language image type grouping — while restating dryRun's behavior. Baseline 3 is appropriate.

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 one PNG/JPEG image'), enumerates the concrete image types, and immediately distinguishes this from delete_image / delete_all_images by describing append-vs-replace semantics. An agent knows exactly what this tool does without opening the schema.

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?

Gives actionable context for the dryRun path ('validate without publishing') and clarifies that filePath must be a local file, which selects this tool over any remote-URL upload path. It does not name a sibling alternative or state when-not-to-use it, so it falls short of the explicit routing that earns a 5.

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

Deploy Server

Other Tools