App Store Connect MCP

Create phased release

create-phased-release

Enable gradual rollout for an approved App Store version by setting the initial phased release state to active, paused, or complete.

Instructions

Enable phased release for an App Store version (gradual rollout to users). Version must be approved or already in release.

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": {
      "appStoreVersionId": "<appStoreVersionId>"
    },
    "name": "create-phased-release"
  }
}

Input Schema

Name	Required	Description	Default
`appStoreVersionId`	Yes	App Store version ID to enable phased release for
`phasedReleaseState`	No	Initial state (INACTIVE, ACTIVE, PAUSED, COMPLETE)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.6Aug 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate a non-read, non-idempotent operation. The description adds the important behavioral constraint that the version must be approved or in release, and explains the meaning as gradual rollout. It is consistent with annotations, though it does not detail state transitions.

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 two short sentences with no wasted words. It front-loads the action and resource, then adds a necessary condition. Every word 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 two-parameter tool without an output schema, the description conveys the core behavior and prerequisite. It does not explain return values, but that is not critical for invocation, and the schema covers the parameters.

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?

The input schema already provides descriptions for both parameters with 100% coverage. The tool description does not add extra meaning beyond the schema, so it meets the baseline.

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 action ('Enable') and the resource ('phased release for an App Store version'), with a clarifying parenthetical ('gradual rollout to users'). It is specific and distinguishes the tool from read-only siblings like get-phased-release.

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?

It provides an explicit precondition ('Version must be approved or already in release'), which tells the agent when it is valid to use the tool. It does not explicitly name alternatives or exclusions, but the precondition scopes usage effectively.

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

Deploy Server