Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_analytics_reports

Retrieve available analytics reports for a specific report request in App Store Connect, filtering by category and controlling result quantity.

Instructions

Get available analytics reports for a specific report request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportRequestIdYesThe ID of the analytics report request
limitNoMaximum number of reports to return (default: 100)
filterNo

Implementation Reference

  • The main handler function that implements the core logic for the 'list_analytics_reports' tool. It validates inputs, builds query parameters, and calls the App Store Connect API to retrieve the list of analytics reports.
    async listAnalyticsReports(args: {
      reportRequestId: string;
      limit?: number;
      filter?: {
        category?: AnalyticsReportCategory;
      };
    }): Promise<ListAnalyticsReportsResponse> {
      const { reportRequestId, limit = 100, filter } = args;
      
      validateRequired(args, ['reportRequestId']);
    
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit)
      };
    
      Object.assign(params, buildFilterParams(filter));
    
      return this.client.get<ListAnalyticsReportsResponse>(`/analyticsReportRequests/${reportRequestId}/reports`, params);
    }
  • The input schema definition for the 'list_analytics_reports' tool, registered in the MCP server's tool list. Defines parameters like reportRequestId, limit, and filter.
    name: "list_analytics_reports",
    description: "Get available analytics reports for a specific report request",
    inputSchema: {
      type: "object",
      properties: {
        reportRequestId: {
          type: "string",
          description: "The ID of the analytics report request"
        },
        limit: {
          type: "number",
          description: "Maximum number of reports to return (default: 100)",
          minimum: 1,
          maximum: 200
        },
        filter: {
          type: "object",
          properties: {
            category: {
              type: "string",
              enum: ["APP_STORE_ENGAGEMENT", "APP_STORE_COMMERCE", "APP_USAGE", "FRAMEWORKS_USAGE", "PERFORMANCE"],
              description: "Filter by report category"
            }
          }
        }
      },
      required: ["reportRequestId"]
    }
  • src/index.ts:1391-1392 (registration)
    The registration of the tool handler in the MCP server's callTool request handler switch statement. Maps the tool name to the AnalyticsHandlers.listAnalyticsReports method.
    case "list_analytics_reports":
      return { toolResult: await this.analyticsHandlers.listAnalyticsReports(args as any) };
  • TypeScript interface defining the response structure for the listAnalyticsReports API call, used in the handler's return type.
    export interface ListAnalyticsReportsResponse {
      data: AnalyticsReport[];
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Get available analytics reports', which implies a read-only operation, but doesn't disclose other traits like pagination behavior, rate limits, authentication needs, or what 'available' means in terms of status or permissions. The description is minimal and lacks context beyond the basic action.

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, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to understand at a glance. Every part of the sentence earns its place by specifying the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., what 'available' entails, error handling), doesn't explain the return format or structure of reports, and provides minimal guidance on usage. For a tool with moderate complexity and no structured support, the description should do more to compensate.

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 67%, with parameters like 'reportRequestId' and 'filter.category' well-described in the schema. The description adds no additional parameter semantics beyond implying the tool is for a 'specific report request', which aligns with the required 'reportRequestId'. Since schema coverage is moderate, the description doesn't compensate for gaps but doesn't detract either, meeting the baseline.

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 'available analytics reports', specifying it's for a 'specific report request'. It distinguishes from siblings like 'create_analytics_report_request' (creation vs. retrieval) and 'list_analytics_report_segments' (reports vs. segments), though it doesn't explicitly contrast with other list tools like 'list_apps' or 'list_beta_groups'.

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 by specifying 'for a specific report request', suggesting it should be used when you have a reportRequestId. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'list_analytics_report_segments' or other list tools, nor does it mention 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