Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

download_analytics_report_segment

Download analytics report segment data from App Store Connect to analyze app performance metrics and user behavior patterns.

Instructions

Download data from an analytics report segment URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
segmentUrlYesThe URL of the analytics report segment to download

Implementation Reference

  • The core handler function that downloads the analytics report segment from the given URL using the AppStoreConnectClient's downloadFromUrl method.
    async downloadAnalyticsReportSegment(args: {
      segmentUrl: string;
    }): Promise<{ data: any; contentType: string; size: string }> {
      const { segmentUrl } = args;
      
      validateRequired(args, ['segmentUrl']);
    
      return this.client.downloadFromUrl(segmentUrl);
    }
  • The input schema definition for the tool, specifying the required 'segmentUrl' parameter.
    {
      name: "download_analytics_report_segment",
      description: "Download data from an analytics report segment URL",
      inputSchema: {
        type: "object",
        properties: {
          segmentUrl: {
            type: "string",
            description: "The URL of the analytics report segment to download"
          }
        },
        required: ["segmentUrl"]
      }
    },
  • src/index.ts:1397-1398 (registration)
    The switch case in the tool call handler that dispatches calls to this tool to the AnalyticsHandlers.downloadAnalyticsReportSegment method.
    case "download_analytics_report_segment":
      return { toolResult: await this.analyticsHandlers.downloadAnalyticsReportSegment(args as any) };
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 the action ('download') but doesn't mention permissions, rate limits, output format (e.g., file type, structure), or side effects. This is inadequate for a tool that likely involves data retrieval and potential constraints.

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 function without unnecessary words. It is front-loaded and wastes no space, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the download returns (e.g., data format, file type) or behavioral aspects like error handling, which are crucial for an analytics tool. This leaves significant gaps for agent understanding.

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 has 100% description coverage, with 'segmentUrl' clearly documented. The description adds no additional meaning beyond the schema, such as URL format examples or validation rules, so it meets the baseline for high schema coverage without compensating value.

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 ('download') and resource ('data from an analytics report segment URL'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_analytics_report_segments' or 'create_analytics_report_request', which would require a 5.

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, such as 'list_analytics_report_segments' for listing segments or 'create_analytics_report_request' for generating reports. It lacks context on prerequisites or exclusions, leaving usage unclear.

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