App Store Connect MCP

Get app store version

get-app-store-version

Read-onlyIdempotent

Retrieve a specific App Store version's metadata, state, and build link to track its status and associated build.

Instructions

Get detailed information about a specific App Store version (metadata, state, build link)

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": "get-app-store-version"
  }
}

Input Schema

Name	Required	Description	Default
`appStoreVersionId`	Yes	App Store Connect app store version ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.6Aug 13, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only and idempotent behavior. The description adds value by specifying the kind of information returned (metadata, state, build link), which is especially helpful given the absence of an output schema. No contradiction with 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 with no redundant words. It directly states the action, resource, and key details, making it highly concise and well-structured.

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

Completeness5/5

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

For a simple one-parameter read tool with strong annotations (readOnly, idempotent, non-destructive), the description is complete enough. It covers the purpose and gives a sense of the return content (metadata, state, build link), which is essential since no output schema exists. The tool's simplicity means no further context is required.

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 schema fully describes the only parameter 'appStoreVersionId' as an 'App Store Connect app store version ID', giving 100% coverage. The tool description does not add extra semantic detail beyond that, so the baseline score 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 verb 'Get' clearly indicates a retrieval operation, and the resource is 'a specific App Store version', distinguishing it from the sibling 'list-app-store-versions' which handles multiple versions. The parenthetical '(metadata, state, build link)' adds specificity about what 'detailed information' includes, making the purpose unambiguous.

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 description implies usage when you need details for a single version (by ID), but it does not explicitly state when to use this tool over the list or update siblings. It lacks direct alternatives or exclusions, so the usage guidance is implied rather than explicit.

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

Deploy Server