Skip to main content
Glama
Sign In
app-publish-mcp

app-publish-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apple_create_screenshot_set

Create a legacy App Store screenshot set for a specific display type; Apple deprecated this approach, so use asset upload and placement tools instead.

Instructions

Legacy: create a screenshot set for a specific display type. 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": {
      "localizationId": "<localizationId>",
      "displayType": "<displayType>"
    },
    "name": "apple_create_screenshot_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
displayTypeYesDisplay type (e.g. APP_IPHONE_67, APP_IPHONE_65, APP_IPAD_PRO_129, APP_IPAD_PRO_3GEN_129)
localizationIdYesVersion Localization ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden itself; it does disclose the critical behavioral trait that the endpoint is deprecated by Apple, which is valuable beyond anything structured. However, it says nothing about prerequisites (auth/scopes), whether the operation is reversible, or what a successful call yields for a mutating legacy endpoint.

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, zero redundancy, with the deprecation warning and preferred alternatives 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 simple two-parameter, non-nested mutation with full schema coverage, the description covers purpose, status, and replacement path. It leaves out what a screenshot set contains and any failure/permission expectations, which is a minor gap but not one that blocks a correct call.

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% with both required parameters documented, including displayType examples, so the schema does the heavy lifting. The description only alludes to display-type scoping and adds no format or constraint detail beyond the schema, meeting the baseline 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?

States a specific verb and resource ('create a screenshot set') scoped to 'a specific display type', and explicitly separates itself from the modern path by naming apple_upload_asset and apple_create_placement. An agent can identify the tool and its status 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 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 directs the agent to two named alternatives with the implied condition (prefer the new asset/placement flow). This is exactly the when-to-use guidance an agent needs to avoid a deprecated path.

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