App Store Connect MCP Server

list_analytics_reports

Retrieve analytics reports for a given request ID, optionally filtered by category like app store engagement or performance.

Instructions

List analytics reports available for a report request. Can filter by category (APP_STORE_ENGAGEMENT, COMMERCE, APP_USAGE, FRAMEWORKS_USAGE, PERFORMANCE).

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": {
      "requestId": "<requestId>"
    },
    "name": "list_analytics_reports"
  }
}

Input Schema

Name	Required	Description
`requestId`	Yes	The analytics report request ID
`category`	No	Filter reports by category
`limit`	No	Maximum number of reports to return (1-200)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0May 29, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It correctly identifies a read operation but does not disclose any additional behavioral traits such as pagination, rate limits, permissions, or side effects. The behavior is minimally transparent.

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 very concise: two sentences front-loading the main purpose and adding one filter detail. Every sentence adds value with no fluff.

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 list tool with three well-described parameters and no output schema, the description is largely complete. It explains the main action and filtering. Minor improvement could include clarifying the origin of requestId or the structure of returned reports.

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 coverage is 100% with descriptions for all parameters. The description mentions the category filter and enum values, but these are already documented in the schema. No additional meaning beyond the schema is provided for requestId or limit.

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 (List), the resource (analytics reports), and the context (available for a report request). It also mentions filtering by category with specific enum values, which distinguishes it from sibling tools like list_analytics_report_instances or list_analytics_report_requests.

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 (listing reports for a request with optional category filter) but does not explicitly state when to use this tool vs alternatives like list_analytics_report_instances or list_analytics_report_segments. No exclusions or prerequisites are mentioned.

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

Deploy Server