Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

get_app_info

Retrieve comprehensive details about an iOS or macOS app from App Store Connect, including version information, beta testing data, pricing, and in-app purchases.

Instructions

Get detailed information about a specific app

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdYesThe ID of the app to get information for
includeNoOptional relationships to include in the response

Implementation Reference

  • The core handler function that executes the get_app_info tool logic by calling the AppStoreConnectClient to fetch detailed information about a specific app using its ID, optionally including related resources.
    async getAppInfo(args: { 
      appId: string; 
      include?: AppIncludeOptions[];
    }): Promise<AppInfoResponse> {
      const { appId, include } = args;
      
      validateRequired(args, ['appId']);
    
      const params: Record<string, any> = {};
      if (include?.length) {
        params.include = include.join(',');
      }
    
      return this.client.get<AppInfoResponse>(`/apps/${appId}`, params);
    }
  • Defines the JSON schema for the input parameters of the get_app_info tool, advertised to MCP clients via the ListTools response. Specifies appId as required and include as optional array of relationships.
      name: "get_app_info",
      description: "Get detailed information about a specific app",
      inputSchema: {
        type: "object", 
        properties: {
          appId: {
            type: "string",
            description: "The ID of the app to get information for"
          },
          include: {
            type: "array",
            items: {
              type: "string",
              enum: [
                "appClips", "appInfos", "appStoreVersions", "availableTerritories",
                "betaAppReviewDetail", "betaGroups", "betaLicenseAgreement", "builds",
                "endUserLicenseAgreement", "gameCenterEnabledVersions", "inAppPurchases",
                "preOrder", "prices", "reviewSubmissions"
              ]
            },
            description: "Optional relationships to include in the response"
          }
        },
        required: ["appId"]
      }
    },
  • src/index.ts:1318-1320 (registration)
    Registers the tool name 'get_app_info' in the MCP CallTool request handler switch statement, dispatching calls to the appHandlers.getAppInfo method and formatting the response.
    const appInfo = await this.appHandlers.getAppInfo(args as any);
    return formatResponse(appInfo);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it 'gets' information (implying read-only), but doesn't mention authentication requirements, rate limits, response format, pagination, or error conditions. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple retrieval tool and front-loads the core functionality.

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 with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'detailed information' means, what format the response takes, or any behavioral constraints. Given the complexity implied by the 'include' parameter with 14 relationship options, more context about the response structure would be valuable.

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 already documents both parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what 'detailed information' includes or how the 'include' parameter affects the response. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('detailed information about a specific app'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'get_bundle_id_info' or 'list_apps' which also retrieve app-related information, preventing a perfect score.

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. With siblings like 'list_apps' for multiple apps and 'get_bundle_id_info' for different resource types, there's no indication of when this specific app info retrieval is preferred or required.

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