Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_app_store_versions

Retrieve all App Store versions for a specific application, with options to filter by platform, version string, or release status.

Instructions

Get all app store versions for a specific app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe ID of the app
limitNoMaximum number of versions to return (default: 100)
filterNoOptional filters for app store versions

Implementation Reference

  • The handler function that executes the tool logic: validates inputs, constructs API parameters with filters, and calls the AppStoreConnectClient to fetch app store versions.
    async listAppStoreVersions(args: {
      appId: string;
      limit?: number;
      filter?: {
        platform?: string;
        versionString?: string;
        appStoreState?: string;
      };
    }): Promise<ListAppStoreVersionsResponse> {
      const { appId, limit = 100, filter } = args;
      
      validateRequired(args, ['appId']);
      
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit),
        'filter[app]': appId
      };
      
      if (filter?.platform) {
        params['filter[platform]'] = filter.platform;
      }
      
      if (filter?.versionString) {
        params['filter[versionString]'] = filter.versionString;
      }
      
      if (filter?.appStoreState) {
        params['filter[appStoreState]'] = filter.appStoreState;
      }
      
      return this.client.get<ListAppStoreVersionsResponse>(
        '/appStoreVersions',
        params
      );
    }
  • The TypeScript interface defining the expected response structure for ListAppStoreVersionsResponse.
    export interface ListAppStoreVersionsResponse {
      data: AppStoreVersion[];
      links?: {
        self: string;
        next?: string;
      };
      meta?: {
        paging: {
          total: number;
          limit: number;
        };
      };
    }
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 'Get all app store versions' but doesn't mention whether this is a read-only operation, if it requires authentication, how results are paginated (beyond the limit parameter), or what the output format looks like. For a list operation with no annotation coverage, this is a significant gap in transparency.

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 without unnecessary words. Every part of it earns its place by clearly stating the tool's function, 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 complexity (3 parameters with nested objects) and lack of annotations or output schema, the description is incomplete. It doesn't address behavioral aspects like pagination, authentication needs, or error handling, which are crucial for an agent to use this tool effectively. The schema covers parameters well, but the description fails to provide necessary context beyond the basic purpose.

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 all parameters (appId, limit, filter). The description adds no additional meaning beyond implying filtering by app, which is already covered in the schema. This meets the baseline of 3 where the schema does the heavy lifting, but the description doesn't enhance parameter understanding.

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 ('Get all') and resource ('app store versions for a specific app'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_app_info' or 'list_apps', which might also retrieve app-related information, so it doesn't fully distinguish itself from alternatives.

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 like 'get_app_info' or 'list_apps'. It lacks context about prerequisites, such as needing an app ID, or exclusions, such as not being suitable for retrieving single versions. This leaves the agent without clear usage direction.

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