Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_analytics_report_segments

Retrieve segmented analytics data for App Store reports to analyze performance across different dimensions with downloadable content.

Instructions

Get segments for a specific analytics report (contains download URLs)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportIdYesThe ID of the analytics report
limitNoMaximum number of segments to return (default: 100)

Implementation Reference

  • The handler function that lists analytics report segments by calling the App Store Connect API with the provided reportId and optional limit.
    async listAnalyticsReportSegments(args: {
      reportId: string;
      limit?: number;
    }): Promise<ListAnalyticsReportSegmentsResponse> {
      const { reportId, limit = 100 } = args;
      
      validateRequired(args, ['reportId']);
    
      return this.client.get<ListAnalyticsReportSegmentsResponse>(`/analyticsReports/${reportId}/segments`, {
        limit: sanitizeLimit(limit)
      });
    }
  • JSON schema defining the input parameters for the list_analytics_report_segments tool.
    name: "list_analytics_report_segments",
    description: "Get segments for a specific analytics report (contains download URLs)",
    inputSchema: {
      type: "object",
      properties: {
        reportId: {
          type: "string",
          description: "The ID of the analytics report"
        },
        limit: {
          type: "number",
          description: "Maximum number of segments to return (default: 100)",
          minimum: 1,
          maximum: 200
        }
      },
      required: ["reportId"]
    }
  • src/index.ts:1394-1395 (registration)
    Tool registration in the CallToolRequestSchema handler switch statement, binding the tool name to the AnalyticsHandlers.listAnalyticsReportSegments method.
    case "list_analytics_report_segments":
      return { toolResult: await this.analyticsHandlers.listAnalyticsReportSegments(args as any) };
  • TypeScript interface defining the response structure for list analytics report segments.
    export interface ListAnalyticsReportSegmentsResponse {
      data: AnalyticsReportSegment[];
    }
Behavior2/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 mentions that segments 'contain download URLs', which adds useful context about the return data. However, it lacks details on permissions, rate limits, pagination, or error handling, which are critical for a tool that likely accesses analytics data.

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, efficient sentence that front-loads the core purpose and includes a key detail about download URLs. There is no wasted text, and it is appropriately sized for the tool's complexity.

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?

Given no annotations and no output schema, the description is minimal but covers the basic purpose. It lacks details on behavioral traits, error cases, or output structure, which would be helpful for an analytics tool. However, it's adequate as a starting point for a read-only operation with clear parameters.

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 description coverage is 100%, so the schema fully documents the parameters (reportId and limit). The description does not add any meaning beyond what the schema provides, such as explaining the format of reportId or how segments are ordered. Baseline 3 is appropriate as the schema handles parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Get' and resource 'segments for a specific analytics report', specifying it retrieves segments with download URLs. It distinguishes from the sibling 'list_analytics_reports' by focusing on segments of a report rather than listing reports themselves, but doesn't explicitly differentiate from 'download_analytics_report_segment'.

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 on when to use this tool versus alternatives like 'download_analytics_report_segment' or 'list_analytics_reports'. The description implies usage for retrieving segments with URLs but doesn't specify contexts, prerequisites, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/concavegit/app-store-connect-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server