google-cloud-console-mcp

Upload store listing image

play_upload_image

Upload a PNG or JPEG to a Google Play store listing image slot for a specific language, so localized app store assets are added to an existing edit.

Instructions

Uploads one image (PNG/JPEG) into a store listing image slot for a language.

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

Input Schema

Name	Required	Description
`editId`	Yes	Edit id returned by play_create_edit
`filePath`	Yes	Absolute local path to the image file
`language`	Yes	BCP-47 language code as used by Play Console, e.g. "en-US", "tr-TR"
`imageType`	Yes	Which image slot in the store listing to operate on
`packageName`	Yes	Play Console package name, e.g. "com.example.app"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses file formats (PNG/JPEG) and that it uploads one image, but omits auth requirements, whether it overwrites an existing slot image, and edit-state prerequisites. For a mutation tool, this leaves key behavioral traits undisclosed.

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, front-loaded sentence with no filler; every word contributes. It is appropriately sized for the tool's simple upload action, though the brevity trades off completeness, which is addressed under contextual completeness.

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

Completeness2/5

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

This is a mutation tool with no annotations and no output schema; the description does not explain the edit lifecycle (create, upload, commit) or whether the uploaded image replaces or appends to a slot. Although the schema documents parameters, the description leaves important workflow context missing for correct invocation.

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 the schema already documents all five parameters, including editId, imageType enum values, and filePath. The description adds only a PNG/JPEG file-type constraint and 'for a language', which is a minor semantic addition; baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a specific verb 'Uploads' and resource 'image' with scope 'store listing image slot for a language', so an agent can distinguish it from play_upload_apk/bundle and play_list_images. It does not explicitly name any sibling alternative, so it stops short of a 5.

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?

There is no when/when-not guidance, no prerequisites such as requiring an editId from play_create_edit or committing the edit afterward, and no alternatives named. The only implied context is the slot, which is not enough to route clearly between this and play_update_listing or play_delete_image.

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

Deploy Server