App Store Connect MCP

Get app

get-app

Read-onlyIdempotent

Retrieve detailed information about a specific app from App Store Connect. Optionally include related data such as app store versions, beta groups, and builds.

Instructions

Get detailed information about a specific app

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>"
    },
    "name": "get-app"
  }
}

Input Schema

Name	Required	Description	Default
`appId`	Yes	App Store Connect app ID
`include`	No	Relationships to include (e.g. appStoreVersions, betaGroups, builds)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.6Aug 13, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description merely repeats 'Get' without adding behavioral details such as the structure of the returned information or any side effects, so it adds little beyond 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, focused sentence without redundant words. It conveys the core purpose directly.

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?

The tool is a simple get-by-ID operation with rich annotations, but the description lacks detail about the response format or the meaning of 'detailed information'. It does not mention that the include parameter can fetch related resources, though the schema does. Overall, it is minimally adequate but leaves room for ambiguity about what data is returned.

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 provides complete descriptions for both parameters: appId is 'App Store Connect app ID' and include lists valid relationship values with an example. Since schema coverage is 100%, the description does not need to elaborate, but it also adds no additional semantic meaning.

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 the specific verb 'Get' with the resource 'app' and explicitly notes 'specific app', distinguishing it from sibling tools like list-apps that retrieve multiple apps. It clearly states the tool returns detailed information about an individual app.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives such as list-apps or get-app-info. The description does not state prerequisites, exclusions, or when to prefer another tool, leaving the agent without selection context.

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

Deploy Server