app-publish-mcp

apple_upload_screenshot

Uploads and commits an App Store screenshot to a screenshot set while preserving its ID for recovery; deprecated by Apple, use asset upload and placement tools instead.

Instructions

Legacy: upload and commit a screenshot while preserving its ID for recovery. Deprecated by Apple; prefer apple_upload_asset and apple_create_placement.

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": {
      "screenshotSetId": "<screenshotSetId>",
      "filePath": "<filePath>",
      "fileName": "<fileName>"
    },
    "name": "apple_upload_screenshot"
  }
}

Input Schema

Name	Required	Description
`fileName`	Yes	File name (e.g. screen1.png)
`filePath`	Yes	Local path to the screenshot image
`fileSize`	No	Expected file size in bytes; the actual file size is always used
`screenshotSetId`	Yes	Screenshot Set ID

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.7.0Oct 25, 2026

changedInput schema / properties / fileSize / description

Previous value: -"File size in bytes"New value: +"Expected file size in bytes; the actual file size is always used"

addedInput schema / properties / fileSize / exclusiveMinimum
```
Added value: +0
```

changedInput schema / properties / fileSize / type

Previous value: -"number"New value: +"integer"

changedInput schema / required

Previous value: -[
-  "screenshotSetId",
-  "filePath",
-  "fileName",
-  "fileSize"
-]New value: +[
+  "screenshotSetId",
+  "filePath",
+  "fileName"
+]

First observedv0.3.1Mar 19, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden. It helpfully discloses that the operation both uploads and commits (mutating state) and preserves the ID for recovery, but says nothing about permissions, failure modes, reversibility, or how commit behaves on error. Adequate but incomplete for a mutation tool with zero annotation coverage.

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 tight sentences with zero waste: the deprecation status and the alternatives are front-loaded. Every clause earns its place.

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 legacy mutation with full schema coverage and no output schema, the description covers purpose, deprecation, and alternatives well. It could disclose a bit more about commit semantics and failure behavior, but an agent has enough to call it correctly or avoid it in favor of the recommended tools.

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 all four parameters are already documented (fileName, filePath, fileSize, screenshotSetId). The description adds no parameter-level meaning beyond the schema, so the baseline 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 specific verbs (upload and commit) plus the resource (screenshot), and explicitly distinguishes itself from the modern siblings apple_upload_asset and apple_create_placement. An agent can identify what it does and how it differs from alternatives without opening any schema.

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?

Explicitly flags the tool as 'Legacy' and 'Deprecated by Apple', and directs the agent to prefer apple_upload_asset and apple_create_placement instead. This is clear when-not-to-use and alternative routing guidance.

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

Deploy Server