Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_bundle_ids

Retrieve registered bundle IDs for your Apple Developer team with filtering, sorting, and pagination options to manage app identifiers.

Instructions

Find and list bundle IDs that are registered to your team

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of bundle IDs to return (default: 100, max: 200)
sortNoSort order for the results
filterNo
includeNoRelated resources to include in the response

Implementation Reference

  • The handler function that lists bundle IDs by querying the App Store Connect API with filters, sorting, limits, and includes.
    async listBundleIds(args: {
      limit?: number;
      sort?: string;
      filter?: {
        identifier?: string;
        name?: string;
        platform?: BundlePlatform;
        seedId?: string;
      };
      include?: string[];
    } = {}): Promise<ListBundleIdsResponse> {
      const { limit = 100, sort, filter, include } = args;
      
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit)
      };
    
      if (sort) {
        params.sort = sort;
      }
    
      Object.assign(params, buildFilterParams(filter));
    
      if (Array.isArray(include) && include.length > 0) {
        params.include = include.join(',');
      }
    
      return this.client.get<ListBundleIdsResponse>('/bundleIds', params);
    }
  • Tool schema definition including name, description, and input validation schema for list_bundle_ids.
      name: "list_bundle_ids",
      description: "Find and list bundle IDs that are registered to your team",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of bundle IDs to return (default: 100, max: 200)",
            minimum: 1,
            maximum: 200
          },
          sort: {
            type: "string",
            description: "Sort order for the results",
            enum: [
              "name", "-name", "platform", "-platform", 
              "identifier", "-identifier", "seedId", "-seedId", "id", "-id"
            ]
          },
          filter: {
            type: "object",
            properties: {
              identifier: { type: "string", description: "Filter by bundle identifier" },
              name: { type: "string", description: "Filter by name" },
              platform: { 
                type: "string", 
                description: "Filter by platform",
                enum: ["IOS", "MAC_OS", "UNIVERSAL"]
              },
              seedId: { type: "string", description: "Filter by seed ID" }
            }
          },
          include: {
            type: "array",
            items: {
              type: "string",
              enum: ["profiles", "bundleIdCapabilities", "app"]
            },
            description: "Related resources to include in the response"
          }
        }
      }
    },
  • src/index.ts:1368-1369 (registration)
    Registers the tool handler dispatch in the MCP server request handler switch statement.
    return { toolResult: await this.bundleHandlers.listBundleIds(args as any) };
  • TypeScript interface for the response structure of listBundleIds.
    export interface ListBundleIdsResponse {
      data: BundleId[];
    }
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 tool 'finds and lists' bundle IDs, implying a read-only operation, but lacks details on permissions, rate limits, pagination, or response format. This is a significant gap for a tool with multiple parameters and no output schema.

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 unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 tool's complexity (4 parameters, nested objects, no output schema) and lack of annotations, the description is incomplete. It doesn't explain the response structure, error handling, or behavioral traits like pagination, which are crucial for effective tool use in this context.

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 75%, providing good documentation for parameters like 'limit', 'sort', and 'include'. The description adds no additional parameter semantics beyond what's in the schema, but the schema's coverage is sufficient to meet the baseline score of 3 for adequate 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 ('Find and list') and resource ('bundle IDs that are registered to your team'), providing a specific purpose. However, it doesn't explicitly differentiate from sibling tools like 'list_apps' or 'get_bundle_id_info', which could also involve bundle IDs, so it doesn't reach the highest 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, such as 'get_bundle_id_info' for detailed info on a single bundle ID or 'list_apps' for broader listings. There's no mention of prerequisites, exclusions, or contextual usage, leaving the agent to infer based on tool names alone.

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