Upload App MCP Server

Overview Schema Source Related Servers Discussions Admin

release_ios

Attach a TestFlight build to an App Store version, create the version if needed, and submit for review; release notes set What's New in every language. Without confirm=true, only previews.

Instructions

Attach a TestFlight build to an App Store version, creating the version if needed, and submit it for review. release_notes sets What's New in every language of the live version. Without confirm=true it only describes what it would do.

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": {
      "app_identifier": "<app_identifier>",
      "app_version": "<app_version>",
      "build_number": "<build_number>"
    },
    "name": "release_ios"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	No
`app_version`	Yes
`build_number`	Yes
`release_notes`	No
`app_identifier`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.8/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 load and does well: it discloses that the version may be created as a side effect, that the tool submits for review (an external, non-trivial action), and that release_notes overwrites What's New in every language of the live version. It omits permission/auth requirements and whether a submitted review can be withdrawn.

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?

Three sentences, front-loaded with the action, then the side effect, then the safety gate. No filler; each sentence adds information an agent needs.

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?

An output schema exists, so return values need no explanation, and the description covers the dry-run gate, version creation, and live-version side effects. Gaps remain around auth/prerequisites and failure or rollback behavior for a review submission.

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 0%, so the description must compensate. It explains confirm (dry-run gate) and release_notes (all-languages What's New) precisely, but leaves app_identifier, app_version, and build_number to inference with no format hints (bundle ID vs numeric App Store ID, build vs version string).

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?

States a specific verb chain and resource: attach a TestFlight build to an App Store version, create the version if missing, and submit for review. That is clearly distinct from upload_ios or status_ios in substance, but the description never names a sibling to route against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The line 'Without confirm=true it only describes what it would do' gives useful invocation guidance for a dry run, but there is no explicit when-to-use-this-vs-alternatives statement (e.g., after upload_ios, instead of manual promotion). Usage context is implied rather than stated.

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

Deploy Server