Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_analytics_report_segments

Fetch downloadable report segments for a specified analytics report instance. Each segment provides a download URL, checksum, and size.

Instructions

List downloadable segments for a report instance. Each segment contains a URL for downloading the report data, along with its checksum and size.

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": {
      "instanceId": "<instanceId>"
    },
    "name": "list_analytics_report_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceIdYesThe analytics report instance ID
limitNoMaximum number of segments to return (1-200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must cover behavioral traits. It mentions each segment contains a URL, checksum, and size, but does not disclose pagination, rate limits, or authentication needs. It is adequate but not rich.

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?

Two sentences with no fluff. The first sentence states the purpose, the second adds key details about segments. Efficient and well-structured.

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?

Given 2 parameters, no output schema, and a straightforward list operation, the description covers the core functionality. However, it does not mention whether results are paginated (though limit implies it) or what happens when no segments exist.

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 describes both parameters (instanceId and limit) with 100% coverage. The description adds no additional meaning for the parameters beyond what the schema provides, so a 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 description specifies the action (list) and the resource (downloadable segments for a report instance) clearly. It also differentiates from sibling tools like list_analytics_report_instances and list_analytics_reports by focusing on segments.

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 does not explicitly state when to use this tool versus alternatives or provide exclusions. It implies usage when needing to list segments for downloading, but lacks explicit guidance.

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

Deploy Server

Other Tools