Skip to main content
Glama
Sign In
App Store Connect MCP

App Store Connect MCP

by beautyfree
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Remove beta testers from group

remove-beta-testers-from-group
Idempotent

Remove one or more beta testers from a TestFlight group by group ID and tester IDs. Use list-beta-testers to find tester IDs.

Instructions

Remove one or more beta testers from a TestFlight group. Tester IDs come from list-beta-testers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "betaGroupId": "<betaGroupId>",
      "betaTesterIds": "<betaTesterIds>"
    },
    "name": "remove-beta-testers-from-group"
  }
}

Input Schema

NameRequiredDescriptionDefault
betaGroupIdYesBeta group ID to remove testers from (required)
betaTesterIdsYesBeta tester ID(s) to remove (one or more; use list-beta-testers to get IDs)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.6

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a minor usage tip about sourcing IDs from list-beta-testers but does not elaborate on side effects, error behavior, or permissions. With annotations carrying the main burden, the description adds limited additional behavioral context.

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 two sentences, front-loaded with the core purpose, and contains no redundant information. It efficiently communicates the operation and a key usage note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple removal tool with two fully described parameters and no output schema, the description is sufficient. It explains the operation and where to obtain the necessary IDs. It does not mention error cases or response format, but these are not required given the tool's simplicity and the annotations.

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 coverage is 100%; both betaGroupId and betaTesterIds are described clearly in the schema. The description reiterates the source for tester IDs but does not add meaning beyond what the schema already provides. Baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Remove one or more beta testers from a TestFlight group,' which is a specific verb, resource, and object. It distinguishes itself from sibling tools like add-beta-testers-to-group and list-beta-testers by its purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear usage context by indicating the operation targets a TestFlight group and specifies that tester IDs must come from list-beta-testers, which serves as a prerequisite. It does not explicitly exclude alternatives, but the sibling naming and verb make the use case obvious.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools