Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

create_bundle_id

Register a new bundle ID for iOS, macOS, or universal app development by specifying identifier, name, and platform to prepare your app for distribution.

Instructions

Register a new bundle ID for app development

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierYesThe bundle ID string (e.g., 'com.example.app')
nameYesA name for the bundle ID
platformYesThe platform for this bundle ID
seedIdNoYour team's seed ID (optional)

Implementation Reference

  • The main handler function that executes the create_bundle_id tool logic by validating inputs, constructing the API request body, and calling the AppStoreConnectClient to POST /bundleIds.
    async createBundleId(args: {
      identifier: string;
      name: string;
      platform: BundlePlatform;
      seedId?: string;
    }): Promise<BundleIdResponse> {
      const { identifier, name, platform, seedId } = args;
      
      validateRequired(args, ['identifier', 'name', 'platform']);
    
      const requestBody: CreateBundleIdRequest = {
        data: {
          type: "bundleIds",
          attributes: {
            identifier,
            name,
            platform,
            seedId
          }
        }
      };
    
      return this.client.post<BundleIdResponse>('/bundleIds', requestBody);
    }
  • src/index.ts:1365-1366 (registration)
    Tool call dispatch in the MCP server request handler that maps 'create_bundle_id' calls to the BundleHandlers.createBundleId method.
    return { toolResult: await this.bundleHandlers.createBundleId(args as any) };
  • The tool schema definition including name, description, and inputSchema for the create_bundle_id tool, used in list tools response.
      name: "create_bundle_id",
      description: "Register a new bundle ID for app development",
      inputSchema: {
        type: "object",
        properties: {
          identifier: {
            type: "string",
            description: "The bundle ID string (e.g., 'com.example.app')"
          },
          name: {
            type: "string",
            description: "A name for the bundle ID"
          },
          platform: {
            type: "string",
            enum: ["IOS", "MAC_OS", "UNIVERSAL"],
            description: "The platform for this bundle ID"
          },
          seedId: {
            type: "string",
            description: "Your team's seed ID (optional)"
          }
        },
        required: ["identifier", "name", "platform"]
      }
    },
  • TypeScript interface defining the CreateBundleIdRequest structure used in the handler for input validation and API request body.
    export interface CreateBundleIdRequest {
      data: {
        type: "bundleIds";
        attributes: {
          identifier: string;
          name: string;
          platform: BundlePlatform;
          seedId?: string;
        };
      };
    }
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 'Register a new bundle ID,' implying a write operation, but fails to mention permissions required, rate limits, side effects, or what happens on success/failure. This leaves critical behavioral traits undocumented for a creation tool.

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 redundancy. It is front-loaded with the core action and resource, making it easy to parse quickly, with no wasted words or unnecessary elaboration.

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 creation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects like permissions, error handling, and return values, which are crucial for safe and effective use. The high schema coverage helps with inputs, but overall context remains insufficient.

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 all parameters (e.g., 'identifier' as the bundle ID string, 'platform' with enum values). The description adds no additional meaning beyond the schema, such as format examples or usage context, 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 action ('Register') and resource ('new bundle ID for app development'), making the purpose evident. It doesn't explicitly differentiate from sibling tools like 'list_bundle_ids' or 'get_bundle_id_info', but the verb 'Register' implies creation versus listing or retrieval, providing some implicit distinction.

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 offers no guidance on when to use this tool versus alternatives, such as 'list_bundle_ids' for viewing existing IDs or 'get_bundle_id_info' for details on a specific ID. It lacks context on prerequisites, exclusions, or typical scenarios for registration, 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