App Store Connect MCP

Get pre-release version

get-pre-release-version

Read-onlyIdempotent

Retrieve detailed information about a specific TestFlight pre-release version by providing its pre-release version ID. Get build details, test information, and availability from App Store Connect.

Instructions

Get detailed information about a specific pre-release (TestFlight) version

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": {
      "preReleaseVersionId": "<preReleaseVersionId>"
    },
    "name": "get-pre-release-version"
  }
}

Input Schema

Name	Required	Description	Default
`preReleaseVersionId`	Yes	App Store Connect pre-release version ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.6Aug 13, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already cover the safety profile, and the description does not contradict them. It adds minimal behavioral context ('TestFlight') but no information about return behavior, permissions, or side effects, which is expected given the annotations.

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?

The description is a single, front-loaded sentence that is concise and free of redundancy. It communicates the core function without waste.

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 read-only tool with one parameter and rich annotations, the description is adequate: it specifies the target resource and that it returns detailed info. However, it does not describe the return structure (no output schema) or that the ID comes from list-pre-release-versions, so it's not fully 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 description coverage is 100%, so the schema fully documents the single parameter 'preReleaseVersionId' as 'App Store Connect pre-release version ID'. The description adds no additional parameter meaning beyond that, so the baseline of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('pre-release (TestFlight) version'), clearly distinguishing this from sibling tools like list-pre-release-versions (which lists all) and get-build (which gets a build). It precisely states the tool's scope.

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 phrase 'a specific' implies the tool is used when you already have an identifier, which is clear context. However, it doesn't explicitly mention alternatives or exclude cases (e.g., 'to list versions, use list-pre-release-versions'), so it falls short of a 5.

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

Deploy Server