Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

get_bundle_id_info

Retrieve detailed information about an App Store Connect bundle ID, including its configuration, capabilities, and associated profiles.

Instructions

Get detailed information about a specific bundle ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bundleIdIdYesThe ID of the bundle ID to get information for
includeNoOptional relationships to include in the response
fieldsNoSpecific fields to include in the response

Implementation Reference

  • The core handler function that implements the get_bundle_id_info tool logic by calling the App Store Connect API to retrieve bundle ID details.
    async getBundleIdInfo(args: {
      bundleIdId: string;
      include?: string[];
      fields?: {
        bundleIds?: string[];
      };
    }): Promise<BundleIdResponse> {
      const { bundleIdId, include, fields } = args;
      
      validateRequired(args, ['bundleIdId']);
    
      const params: Record<string, any> = {};
    
      Object.assign(params, buildFieldParams(fields));
    
      if (include?.length) {
        params.include = include.join(',');
      }
    
      return this.client.get<BundleIdResponse>(`/bundleIds/${bundleIdId}`, params);
    }
  • MCP tool schema definition including input schema, description, and parameters for the get_bundle_id_info tool.
      name: "get_bundle_id_info",
      description: "Get detailed information about a specific bundle ID",
      inputSchema: {
        type: "object",
        properties: {
          bundleIdId: {
            type: "string",
            description: "The ID of the bundle ID to get information for"
          },
          include: {
            type: "array",
            items: {
              type: "string",
              enum: ["profiles", "bundleIdCapabilities", "app"]
            },
            description: "Optional relationships to include in the response"
          },
          fields: {
            type: "object",
            properties: {
              bundleIds: {
                type: "array",
                items: {
                  type: "string",
                  enum: ["name", "platform", "identifier", "seedId"]
                },
                description: "Fields to include for the bundle ID"
              }
            },
            description: "Specific fields to include in the response"
          }
        },
        required: ["bundleIdId"]
      }
    },
  • src/index.ts:1370-1372 (registration)
    Tool registration and dispatch logic that maps the 'get_bundle_id_info' tool call to the BundleHandlers.getBundleIdInfo method.
    case "get_bundle_id_info":
      return { toolResult: await this.bundleHandlers.getBundleIdInfo(args as any) };
  • TypeScript interface defining the expected response structure for bundle ID information, used by the handler.
    export interface BundleIdResponse {
      data: BundleId;
    }
  • src/index.ts:76-76 (registration)
    Instantiation of the BundleHandlers class instance used for all bundle-related tools including get_bundle_id_info.
    this.bundleHandlers = new BundleHandlers(this.client);
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 it 'gets detailed information', implying a read-only operation, but doesn't cover aspects like authentication needs, rate limits, error handling, or what 'detailed information' entails (e.g., response format, pagination). This leaves significant gaps for an AI agent to understand how to invoke it correctly.

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 ('Get detailed information about a specific bundle ID') with zero waste. It's appropriately sized for a simple retrieval tool, making it easy for an AI agent to parse quickly.

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

Completeness3/5

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

Given the tool's moderate complexity (3 parameters, nested objects, no output schema) and lack of annotations, the description is minimally adequate but incomplete. It covers the basic purpose but fails to address behavioral aspects like response format or usage context, which are crucial for correct invocation. Without an output schema, the description should ideally hint at return values, but it doesn't.

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 all parameters (bundleIdId, include, fields) with descriptions and enums. The description adds no additional meaning beyond what's in the schema, such as explaining the purpose of 'include' or 'fields' in practical terms. Baseline 3 is appropriate as the 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 the resource 'detailed information about a specific bundle ID', making the purpose understandable. However, it doesn't differentiate this tool from similar siblings like 'get_app_info' or 'list_bundle_ids', which would require mentioning it retrieves details for a single, specific bundle ID rather than listing or getting app information.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify that this is for retrieving details of a single bundle ID (vs. 'list_bundle_ids' for multiple) or clarify its relationship to other get_* tools like 'get_app_info'. The description implies usage by stating 'specific bundle ID' but lacks explicit context 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