Skip to main content
Glama
Sign In
appstore-connect-mcp

appstore-connect-mcp

by tomoki013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[Write] Upload a screenshot

asc_screenshot_upload

Upload a local screenshot file to App Store Connect for a specific version, locale, and display type, creating the screenshot set if it doesn't exist.

Instructions

Write. Uploads a local screenshot image file to App Store Connect for a version/locale/display type, creating the screenshot set first if one doesn't already exist for that display type.

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": {
      "appId": "<appId>",
      "version": "<version>",
      "locale": "<locale>",
      "screenshotDisplayType": "<screenshotDisplayType>",
      "filePath": "<filePath>"
    },
    "name": "asc_screenshot_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
appIdYesBundle id, app name, or App Store Connect app id
localeYesLocale, e.g. "en-US"
versionYesApp Store version string, e.g. "1.1"
filePathYesAbsolute local path to the screenshot image file
screenshotDisplayTypeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/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 full burden. It does disclose a key side effect (creating the screenshot set if it doesn't exist), which is useful. However, it does not mention permissions, idempotency, whether existing screenshots are replaced, or prerequisites like an existing version/locale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, front-loaded with the main verb 'Uploads'. The 'Write.' prefix is somewhat redundant but not bloated. It is efficient and readable.

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

Completeness3/5

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

For a five-parameter mutation tool with no annotations and no output schema, the description covers the main action and one side effect, but lacks information about return values, prerequisites (e.g., app/version existence), and potential failure modes. This is adequate but not complete.

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 80% (4 of 5 parameters have descriptions; screenshotDisplayType has an enum). The description adds modest context by linking screenshotDisplayType to the screenshot set creation logic, but otherwise repeats parameter names. Baseline 3 applies due to high coverage.

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 clearly states the tool uploads a local screenshot file to App Store Connect for a specific version/locale/display type, and it distinguishes itself from sibling tools like asc_screenshot_delete by specifying the action and the screenshot set creation side effect.

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?

The description gives a clear context of when to use the tool (for uploading screenshots to a specific version/locale/display type) but does not explicitly mention when not to use it or name alternatives. The 'Write.' prefix and the upload verb imply mutation, which is sufficient for selection.

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