Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

list_beta_groups

List beta tester groups for an app, returning group name, internal/external status, and feedback settings.

Instructions

List beta tester groups for an app. Returns group name, internal/external status, and feedback settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesApp Store Connect app ID
limitNoMaximum number of groups to return (default: 50)

Implementation Reference

  • src/index.ts:76-86 (registration)
    Registration of the 'list_beta_groups' tool with the MCP server. Binds the schema and handler.
    server.tool(
      "list_beta_groups",
      "List beta tester groups for an app. Returns group name, internal/external status, and feedback settings.",
      listGroupsSchema.shape,
      async (args) => {
        const result = await handleListGroups(client, args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Handler function `handleListGroups` that processes the tool invocation, calls the API, and maps results.
    export async function handleListGroups(
      client: AppStoreConnectClient,
      args: z.infer<typeof listGroupsSchema>
    ) {
      const groups = await listBetaGroups(client, args.app_id, {
        limit: args.limit,
      });
    
      return groups.map((g) => ({
        id: g.id,
        name: g.attributes.name,
        isInternalGroup: g.attributes.isInternalGroup,
        publicLinkEnabled: g.attributes.publicLinkEnabled,
        feedbackEnabled: g.attributes.feedbackEnabled,
      }));
    }
  • Zod schema `listGroupsSchema` defining input validation (app_id required, limit optional).
    export const listGroupsSchema = z.object({
      app_id: z.string().describe("App Store Connect app ID"),
      limit: z
        .number()
        .min(1)
        .max(200)
        .optional()
        .describe("Maximum number of groups to return (default: 50)"),
    });
  • API function `listBetaGroups` that makes the actual App Store Connect API request to /betaGroups.
    export async function listBetaGroups(
      client: AppStoreConnectClient,
      appId: string,
      options?: { limit?: number }
    ): Promise<BetaGroup[]> {
      const params: Record<string, string> = {
        "filter[app]": appId,
        "fields[betaGroups]":
          "name,isInternalGroup,publicLinkEnabled,publicLinkLimit,publicLink,feedbackEnabled",
        limit: String(options?.limit ?? 50),
      };
    
      const response = await client.requestAll<BetaGroup>(
        "/betaGroups",
        params
      );
      return response.data;
    }
  • Type definitions `BetaGroupAttributes` and `BetaGroup` used by the API response.
    // Beta Groups
    export interface BetaGroupAttributes {
      name: string;
      isInternalGroup: boolean;
      publicLinkEnabled: boolean;
      publicLinkLimit: number | null;
      publicLink: string | null;
      feedbackEnabled: boolean;
    }
    
    export interface BetaGroup extends JsonApiResource {
      type: "betaGroups";
      attributes: BetaGroupAttributes;
    }
Behavior2/5

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

Annotations are absent, and the description does not disclose behavioral traits such as idempotency, rate limits, or side effects. The tool appears to be a read operation, but this is not explicitly stated.

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?

Description is a single concise sentence with no redundant information. It is front-loaded with the main action and result.

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?

No output schema is provided, and the description only briefly mentions return fields. Lacks details on pagination, sorting, or other behaviors that might be needed given the absence of 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 description coverage is 100%, so parameters are adequately described in the schema. The description adds value by mentioning what the response includes, but this is not necessary for parameter understanding.

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 tester groups for an app and specifies the returned information (group name, status, feedback settings). It distinguishes from siblings like list_beta_testers or list_apps.

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?

No guidance on when to use this tool versus alternatives like list_beta_testers or list_feedback. The description does not provide context for choosing this tool.

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