Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

add_tester_to_group

Add a new tester to an App Store Connect beta testing group by providing their email, first name, last name, and the group ID to enable app testing.

Instructions

Add a new tester to a beta group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe ID of the beta group
emailYesEmail address of the tester
firstNameYesFirst name of the tester
lastNameYesLast name of the tester

Implementation Reference

  • Implementation of the addTesterToGroup handler function that creates a new beta tester and adds them to the specified beta group via the App Store Connect API.
    async addTesterToGroup(args: {
      groupId: string;
      email: string;
      firstName: string;
      lastName: string;
    }): Promise<ListBetaTestersResponse> {
      const { groupId, email, firstName, lastName } = args;
      
      validateRequired(args, ['groupId', 'email', 'firstName', 'lastName']);
    
      const requestBody: AddTesterRequest = {
        data: {
          type: "betaTesters",
          attributes: {
            email,
            firstName,
            lastName
          },
          relationships: {
            betaGroups: {
              data: [{
                id: groupId,
                type: "betaGroups"
              }]
            }
          }
        }
      };
    
      return this.client.post<ListBetaTestersResponse>('/betaTesters', requestBody);
    }
  • Tool schema definition for 'add_tester_to_group' including input schema with required parameters: groupId, email, firstName, lastName.
      name: "add_tester_to_group",
      description: "Add a new tester to a beta group",
      inputSchema: {
        type: "object",
        properties: {
          groupId: {
            type: "string",
            description: "The ID of the beta group"
          },
          email: {
            type: "string",
            description: "Email address of the tester"
          },
          firstName: {
            type: "string",
            description: "First name of the tester"
          },
          lastName: {
            type: "string",
            description: "Last name of the tester"
          }
        },
        required: ["groupId", "email", "firstName", "lastName"]
      }
    },
  • src/index.ts:1328-1329 (registration)
    Registration of the 'add_tester_to_group' tool in the MCP server request handler switch statement, dispatching to betaHandlers.addTesterToGroup.
    case "add_tester_to_group":
      return { toolResult: await this.betaHandlers.addTesterToGroup(args as any) };
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 the write operation ('Add') but lacks critical details: whether this requires specific permissions, if it's idempotent (e.g., adding an existing tester), what happens on success/failure, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loaded with the core action, making it easy to parse.

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 complexity (a write operation with 4 required parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, idempotency, or error handling, nor does it explain what the tool returns. For a mutation tool, this leaves significant gaps for an agent to use it correctly.

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 four parameters (groupId, email, firstName, lastName) with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. This meets the baseline for high schema coverage.

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 ('Add') and target resource ('a new tester to a beta group'), making the purpose immediately understandable. It distinguishes from the sibling tool 'remove_tester_from_group' by specifying the opposite operation. However, it doesn't explicitly differentiate from other sibling tools like 'list_group_testers' beyond the verb, which prevents 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. It doesn't mention prerequisites (e.g., needing an existing beta group), exclusions, or comparisons to sibling tools like 'list_group_testers' for checking existing testers. The agent must infer usage from the tool name 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