Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

list_beta_testers

List TestFlight beta testers filtered by app, group, or email. Returns tester details including name, email, invite type, and state.

Instructions

List beta testers. Filter by app, group, or email. Returns tester name, email, invite type, and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idNoFilter testers by app ID
group_idNoFilter testers by beta group ID
emailNoFilter by tester email address
limitNoMaximum number of testers to return (default: 50)

Implementation Reference

  • src/index.ts:64-74 (registration)
    Registration of the 'list_beta_testers' tool via server.tool(), wiring the schema and handler together.
    server.tool(
      "list_beta_testers",
      "List beta testers. Filter by app, group, or email. Returns tester name, email, invite type, and state.",
      listTestersSchema.shape,
      async (args) => {
        const result = await handleListTesters(client, args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Handler function handleListTesters that orchestrates the beta tester listing logic, calling the API and mapping results.
    export async function handleListTesters(
      client: AppStoreConnectClient,
      args: z.infer<typeof listTestersSchema>
    ) {
      const { testers } = await listBetaTesters(client, {
        appId: args.app_id,
        groupId: args.group_id,
        email: args.email,
        limit: args.limit,
      });
    
      return testers.map((t) => ({
        id: t.id,
        firstName: t.attributes.firstName,
        lastName: t.attributes.lastName,
        email: t.attributes.email,
        inviteType: t.attributes.inviteType,
        state: t.attributes.state,
      }));
    }
  • Zod schema for input validation: optional app_id, group_id, email, and limit fields.
    export const listTestersSchema = z.object({
      app_id: z
        .string()
        .optional()
        .describe("Filter testers by app ID"),
      group_id: z
        .string()
        .optional()
        .describe("Filter testers by beta group ID"),
      email: z
        .string()
        .optional()
        .describe("Filter by tester email address"),
      limit: z
        .number()
        .min(1)
        .max(200)
        .optional()
        .describe("Maximum number of testers to return (default: 50)"),
    });
  • API helper function listBetaTesters that builds query parameters, calls the App Store Connect API's /betaTesters endpoint, and returns the result.
    export async function listBetaTesters(
      client: AppStoreConnectClient,
      options?: ListTestersOptions
    ): Promise<{ testers: BetaTester[]; included: JsonApiResource[] }> {
      const params: Record<string, string> = {
        "fields[betaTesters]": "firstName,lastName,email,inviteType,state",
        limit: String(options?.limit ?? 50),
        sort: options?.sort ?? "lastName",
      };
    
      if (options?.appId) {
        params["filter[apps]"] = options.appId;
      }
      if (options?.groupId) {
        params["filter[betaGroups]"] = options.groupId;
      }
      if (options?.email) {
        params["filter[email]"] = options.email;
      }
    
      const response = await client.requestAll<BetaTester>("/betaTesters", params);
      return { testers: response.data, included: response.included };
    }
Behavior3/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 correctly indicates a read-only list operation and describes returned fields, but it omits details like pagination, sorting, or potential side effects. Adequate but not thorough.

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?

Two sentences with no redundant information. Every phrase adds value: action, filters, and output fields.

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?

The description covers core purpose and filters but lacks details on default limit, pagination, or ordering. With 4 optional parameters and no output schema, more context (e.g., 'returns up to 50 testers by default') would improve completeness.

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?

Input schema has 100% description coverage, each parameter is documented. The description adds that the tool returns specific fields, but does not enrich parameter meaning beyond the schema. Baseline score applies.

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 tool lists beta testers and specifies filter options (app, group, email) and return fields (name, email, invite type, state). This differentiates it from sibling tools like list_beta_groups.

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 lists filter parameters and implies when to use (listing testers with optional filters). It does not explicitly exclude alternatives, but the context is clear and sufficient for a list operation.

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/BandaruDheeraj/testflight-feedback-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server