App Store Connect MCP

Get subscription

get-subscription

Read-onlyIdempotent

Retrieve complete details for a subscription by ID: productId, name, state, pricing, review screenshot, and introductory or promotional offers.

Instructions

Get one subscription by ID: productId, name, state, prices, review screenshot, introductory/promotional offers, etc.

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": {
      "subscriptionId": "<subscriptionId>"
    },
    "name": "get-subscription"
  }
}

Input Schema

Name	Required	Description	Default
`subscriptionId`	Yes	Subscription ID (from list-subscription-group-subscriptions or app subscription groups)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.6Aug 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds useful detail about the response content (fields included), but does not disclose other behaviors such as error handling or not-found scenarios. This adds some value but is not extensive.

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 immediately states the action and scope, listing a few illustrative fields without verbosity. Every word contributes to clarity.

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?

This is a simple, single-parameter read tool with strong annotations and a clear sibling context. The description gives enough detail about return content to allow correct invocation, and the output schema is not needed given the straightforward nature.

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 documents the single parameter with a description ('Subscription ID...'), giving 100% coverage. The tool description does not add further parameter semantics, so the baseline of 3 applies—the schema carries the load.

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') with a clear resource ('one subscription by ID') and enumerates the returned fields (productId, name, state, prices, etc.). This clearly distinguishes it from the sibling list tool, which retrieves multiple subscriptions.

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 description implies the tool is for fetching a single subscription when the ID is known, which gives clear context. However, it does not explicitly name alternatives like the sibling list-subscription-group-subscriptions, so it stops 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