Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_group_testers

Retrieve all testers in a TestFlight beta group by group ID to review or manage beta participants.

Instructions

Get a list of all testers in a specific beta group

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": {
      "groupId": "<groupId>"
    },
    "name": "list_group_testers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of testers to return (default: 100)
groupIdYesThe ID of the beta group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that the tool is read-only, does not describe pagination behavior despite a limit parameter, and lacks information about permissions or error conditions.

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, straightforward sentence with no wasted words. It is front-loaded with the verb and clearly states the purpose.

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 has two parameters and no output schema, the description should provide more context about the return format, pagination behavior, or error handling. It is incomplete and does not cover these aspects.

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% (both parameters have descriptions in the schema). The description does not add any extra meaning beyond what the schema provides, so it meets the baseline of 3.

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 uses the verb 'Get' and specifies the resource as 'a list of all testers in a specific beta group', which clearly identifies the tool's action and distinguishes it from siblings like 'add_tester_to_group' and 'remove_tester_from_group'. However, the word 'all' contradicts the presence of a limit parameter, causing minor ambiguity.

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

Usage Guidelines3/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The usage is implied by the contrast with sibling tools (add/remove), but there is no direct statement about alternatives or exclusions.

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