Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

create_analytics_report_request

Generate analytics reports for an app in App Store Connect to monitor performance metrics and historical data.

Instructions

Create a new analytics report request for an app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe ID of the app to generate analytics reports for
accessTypeNoAccess type for the analytics report (ONGOING for daily data, ONE_TIME_SNAPSHOT for historical data)ONE_TIME_SNAPSHOT

Implementation Reference

  • The handler function that creates a new analytics report request for the specified app by constructing the API request body and calling the AppStoreConnectClient.post method.
    async createAnalyticsReportRequest(args: {
      appId: string;
      accessType?: AnalyticsAccessType;
    }): Promise<AnalyticsReportRequestResponse> {
      const { appId, accessType = "ONE_TIME_SNAPSHOT" } = args;
      
      validateRequired(args, ['appId']);
    
      const requestBody: AnalyticsReportRequest = {
        data: {
          type: "analyticsReportRequests",
          attributes: {
            accessType
          },
          relationships: {
            app: {
              data: {
                id: appId,
                type: "apps"
              }
            }
          }
        }
      };
    
      return this.client.post<AnalyticsReportRequestResponse>('/analyticsReportRequests', requestBody);
    }
  • MCP tool schema definition including name, description, and input schema validation for the create_analytics_report_request tool.
      name: "create_analytics_report_request",
      description: "Create a new analytics report request for an app",
      inputSchema: {
        type: "object",
        properties: {
          appId: {
            type: "string",
            description: "The ID of the app to generate analytics reports for"
          },
          accessType: {
            type: "string",
            enum: ["ONGOING", "ONE_TIME_SNAPSHOT"],
            description: "Access type for the analytics report (ONGOING for daily data, ONE_TIME_SNAPSHOT for historical data)",
            default: "ONE_TIME_SNAPSHOT"
          }
        },
        required: ["appId"]
      }
    },
  • src/index.ts:1388-1389 (registration)
    Registers the tool name to the handler method in the MCP server request handler switch statement.
    case "create_analytics_report_request":
      return { toolResult: await this.analyticsHandlers.createAnalyticsReportRequest(args as any) };
  • TypeScript interfaces defining the request body and response structure for the analytics report request API.
    export interface AnalyticsReportRequest {
      data: {
        type: 'analyticsReportRequests';
        attributes: {
          accessType: AnalyticsAccessType;
        };
        relationships: {
          app: {
            data: {
              id: string;
              type: 'apps';
            };
          };
        };
      };
    }
  • src/index.ts:79-79 (registration)
    Instantiates the AnalyticsHandlers class instance used by the tool.
    this.analyticsHandlers = new AnalyticsHandlers(this.client, appConfig);
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 of behavioral disclosure. It states 'Create' implies a write operation but doesn't cover critical aspects like permissions required, whether the request is asynchronous, rate limits, or what happens after creation (e.g., report generation time). This leaves significant gaps in understanding the tool's behavior beyond basic intent.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly, which is ideal for conciseness in tool descriptions.

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?

For a tool that creates analytics report requests with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., async nature, permissions), expected outcomes, or error handling. Given the complexity of initiating analytics reports, more context is needed to guide the agent effectively beyond the basic action stated.

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%, with clear documentation for both parameters (appId and accessType with enum values). The description adds no additional parameter semantics beyond what's in the schema, such as explaining the implications of 'ONGOING' vs 'ONE_TIME_SNAPSHOT' in more detail. Given the high schema coverage, a baseline score of 3 is appropriate as the schema adequately 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 action ('Create') and resource ('analytics report request for an app'), making the purpose evident. However, it doesn't explicitly differentiate this tool from sibling tools like 'list_analytics_reports' or 'download_analytics_report_segment', which would require mentioning it's specifically for initiating report generation rather than listing or retrieving existing ones.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an app ID), exclusions, or compare it to related tools like 'list_analytics_reports' for existing data, leaving the agent to infer usage context solely from the tool name and parameters.

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