Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_beta_groups

Retrieve all internal and external beta testing groups for iOS/macOS apps to manage testers and distribution through App Store Connect.

Instructions

Get a list of all beta groups (internal and external)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of groups to return (default: 100)

Implementation Reference

  • The main handler function that executes the tool logic by querying the App Store Connect API for beta groups.
    async listBetaGroups(args: { limit?: number } = {}): Promise<ListBetaGroupsResponse> {
      const { limit = 100 } = args;
      
      return this.client.get<ListBetaGroupsResponse>('/betaGroups', {
        limit: sanitizeLimit(limit),
        include: 'app,betaTesters'
      });
    }
  • src/index.ts:1322-1324 (registration)
    Registers the tool call handler in the MCP server's switch statement, dispatching to BetaHandlers.listBetaGroups.
    case "list_beta_groups":
      return { toolResult: await this.betaHandlers.listBetaGroups(args as any) };
  • src/index.ts:134-147 (registration)
    Tool registration including name, description, and input schema definition returned in listTools.
    {
      name: "list_beta_groups",
      description: "Get a list of all beta groups (internal and external)",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of groups to return (default: 100)",
            minimum: 1,
            maximum: 200
          }
        }
      }
  • TypeScript interfaces defining the BetaGroup structure and ListBetaGroupsResponse used for type safety in handler and responses.
    export interface BetaGroup {
      id: string;
      type: string;
      attributes: {
        name: string;
        isInternalGroup: boolean;
        publicLinkEnabled: boolean;
        publicLinkId?: string;
        publicLinkLimit?: number;
        createdDate: string;
      };
    }
    
    export interface BetaTester {
      id: string;
      type: string;
      attributes: {
        firstName: string;
        lastName: string;
        email: string;
        inviteType: string;
        betaGroups?: BetaGroup[];
      };
    }
    
    export interface ListBetaGroupsResponse {
      data: BetaGroup[];
    }
    
    export interface ListBetaTestersResponse {
      data: BetaTester[];
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets a list' but doesn't disclose behavioral traits like pagination, rate limits, authentication needs, or what 'all' entails (e.g., completeness guarantees). This is inadequate for a list operation without annotation support.

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 with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple list tool, making it easy 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 low complexity (1 optional parameter, no output schema), the description is minimally adequate. However, without annotations or output schema, it lacks details on return format or behavioral constraints, leaving gaps for an AI agent to infer.

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 the 'limit' parameter. The description adds no parameter-specific information beyond what the schema provides, meeting the baseline for high coverage but not adding extra 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 verb ('Get') and resource ('list of all beta groups'), specifying both internal and external groups. It distinguishes from siblings like 'list_group_testers' or 'list_users' by focusing on beta groups specifically, though it doesn't explicitly contrast with them.

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. While siblings like 'list_group_testers' or 'list_apps' exist, the description doesn't mention them or specify contexts where this tool is preferred, 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