Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

remove_tester_from_group

Remove a beta tester from a beta testing group in App Store Connect to manage test access and group composition.

Instructions

Remove a tester from a beta group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe ID of the beta group
testerIdYesThe ID of the beta tester

Implementation Reference

  • The main handler function that performs the API DELETE request to remove the specified tester from the beta group.
    async removeTesterFromGroup(args: {
      groupId: string;
      testerId: string;
    }): Promise<{ success: boolean; message: string }> {
      const { groupId, testerId } = args;
      
      validateRequired(args, ['groupId', 'testerId']);
    
      const requestBody: RemoveTesterRequest = {
        data: [{
          id: testerId,
          type: "betaTesters"
        }]
      };
    
      await this.client.delete(`/betaGroups/${groupId}/relationships/betaTesters`, requestBody);
    
      return { 
        success: true, 
        message: "Tester removed from group successfully" 
      };
    }
  • JSON schema defining the input parameters: groupId and testerId as required strings.
    inputSchema: {
      type: "object",
      properties: {
        groupId: {
          type: "string",
          description: "The ID of the beta group"
        },
        testerId: {
          type: "string",
          description: "The ID of the beta tester"
        }
      },
      required: ["groupId", "testerId"]
    }
  • src/index.ts:196-212 (registration)
    Tool registration in the buildToolsList() array, defining name, description, and schema.
      name: "remove_tester_from_group",
      description: "Remove a tester from a beta group",
      inputSchema: {
        type: "object",
        properties: {
          groupId: {
            type: "string",
            description: "The ID of the beta group"
          },
          testerId: {
            type: "string",
            description: "The ID of the beta tester"
          }
        },
        required: ["groupId", "testerId"]
      }
    },
  • src/index.ts:1332-1333 (registration)
    Dispatch registration in the CallToolRequest handler switch statement, binding the tool name to the betaHandlers.removeTesterFromGroup method.
    return { toolResult: await this.betaHandlers.removeTesterFromGroup(args as any) };
  • TypeScript interface used in the handler for the request body structure sent to the App Store Connect API.
    export interface RemoveTesterRequest {
      data: Array<{
        id: string;
        type: "betaTesters";
      }>;
    }
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 action is a removal (implying mutation/destructive), but doesn't specify whether this requires special permissions, is reversible, has side effects, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 function without unnecessary words. It's front-loaded with the core action and resource, making it immediately scannable and understandable. Every word earns its place.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after removal (e.g., confirmation message, error responses), doesn't mention dependencies or prerequisites, and provides no behavioral context. The agent would need to guess about success criteria and side effects.

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?

The description doesn't add any parameter-specific information beyond what's already in the schema (which has 100% coverage). Both parameters are documented in the schema with clear descriptions. The description implies the parameters are needed but doesn't explain their format, source, or relationships, so it 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 ('Remove') and the target ('a tester from a beta group'), making the purpose immediately understandable. It doesn't explicitly differentiate from its sibling 'add_tester_to_group', but the verb 'Remove' versus 'Add' provides implicit distinction. The description avoids tautology by specifying what's being removed from what.

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., the tester must already be in the group), error conditions, or relationships with other tools like 'list_group_testers' for verification. 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