Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

list_feedback

Retrieve and filter TestFlight feedback for an app, including screenshots, crash reports, and text comments. Filter by build or feedback type.

Instructions

List TestFlight feedback for an app. Retrieves screenshot submissions, crash reports, and (with browser auth) text comments. Filter by build or feedback type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesApp Store Connect app ID
build_idNoFilter feedback by build ID
typeNoType of feedback to retrieve. 'comments' requires browser auth. Default: 'all'
limitNoMaximum number of feedback items per type (default: 50)

Implementation Reference

  • Main handler function for the list_feedback tool. Fetches screenshot, crash, and text comment feedback from multiple sources, sorts by timestamp, and returns unified FeedbackItem array.
    export async function handleListFeedback(
      client: AppStoreConnectClient,
      args: z.infer<typeof listFeedbackSchema>
    ): Promise<{
      feedback: FeedbackItem[];
      sources: string[];
      note?: string;
    }> {
      const feedbackType = args.type ?? "all";
      const allFeedback: FeedbackItem[] = [];
      const sources: string[] = [];
      let note: string | undefined;
    
      const opts = {
        appId: args.app_id,
        buildId: args.build_id,
        limit: args.limit,
      };
    
      // Screenshot feedback (official API)
      if (feedbackType === "all" || feedbackType === "screenshots") {
        try {
          const { submissions, included } = await listScreenshotFeedback(client, opts);
          const items = toFeedbackItems(submissions, included, "screenshot");
          allFeedback.push(...items);
          sources.push("official-api:screenshots");
        } catch (error) {
          note = `Screenshot feedback fetch failed: ${error instanceof Error ? error.message : String(error)}`;
        }
      }
    
      // Crash feedback (official API)
      if (feedbackType === "all" || feedbackType === "crashes") {
        try {
          const { submissions, included } = await listCrashFeedback(client, opts);
          const items = toFeedbackItems(submissions, included, "crash");
          allFeedback.push(...items);
          sources.push("official-api:crashes");
        } catch (error) {
          const msg = `Crash feedback fetch failed: ${error instanceof Error ? error.message : String(error)}`;
          note = note ? `${note}; ${msg}` : msg;
        }
      }
    
      // Text comments (iris API, requires browser auth)
      if (feedbackType === "all" || feedbackType === "comments") {
        const irisFeedback = await listIrisFeedback(args.app_id, {
          buildId: args.build_id,
          limit: args.limit,
        });
        if (irisFeedback) {
          allFeedback.push(...irisFeedback);
          sources.push("iris-api:comments");
        } else if (feedbackType === "comments") {
          note = note
            ? `${note}; Text comments require ENABLE_BROWSER_AUTH=true`
            : "Text comments require ENABLE_BROWSER_AUTH=true with ASC_USERNAME and ASC_PASSWORD set.";
        }
      }
    
      // Sort all by timestamp descending
      allFeedback.sort(
        (a, b) => new Date(b.timestamp).getTime() - new Date(a.timestamp).getTime()
      );
    
      return { feedback: allFeedback, sources, note };
    }
  • Zod schema for list_feedback input validation: app_id (required), build_id (optional), type (all/screenshots/crashes/comments, optional), limit (1-200, optional).
    export const listFeedbackSchema = z.object({
      app_id: z.string().describe("App Store Connect app ID"),
      build_id: z
        .string()
        .optional()
        .describe("Filter feedback by build ID"),
      type: z
        .enum(["all", "screenshots", "crashes", "comments"])
        .optional()
        .describe(
          "Type of feedback to retrieve. 'comments' requires browser auth. Default: 'all'"
        ),
      limit: z
        .number()
        .min(1)
        .max(200)
        .optional()
        .describe("Maximum number of feedback items per type (default: 50)"),
    });
  • src/index.ts:88-98 (registration)
    Registration of the 'list_feedback' tool with the MCP server, linking the schema and handler.
    server.tool(
      "list_feedback",
      "List TestFlight feedback for an app. Retrieves screenshot submissions, crash reports, and (with browser auth) text comments. Filter by build or feedback type.",
      listFeedbackSchema.shape,
      async (args) => {
        const result = await handleListFeedback(client, args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • toFeedbackItems helper: converts raw API submissions (screenshot/crash) into unified FeedbackItem format.
    export function toFeedbackItems(
      submissions: (BetaFeedbackScreenshotSubmission | BetaFeedbackCrashSubmission)[],
      included: JsonApiResource[],
      type: "screenshot" | "crash"
    ): FeedbackItem[] {
      return submissions.map((sub) => {
        const testerRef = sub.relationships?.betaTester?.data;
        const buildRef = sub.relationships?.build?.data;
    
        const tester =
          testerRef && !Array.isArray(testerRef)
            ? included.find(
                (r) => r.type === "betaTesters" && r.id === testerRef.id
              )
            : null;
        const build =
          buildRef && !Array.isArray(buildRef)
            ? included.find((r) => r.type === "builds" && r.id === buildRef.id)
            : null;
    
        const testerAttrs = tester?.attributes as
          | { firstName?: string; lastName?: string; email?: string }
          | undefined;
        const buildAttrs = build?.attributes as
          | { version?: string }
          | undefined;
    
        const attrs = sub.attributes as unknown as Record<string, unknown>;
        const screenshotAsset = attrs.screenshotAsset as
          | { templateUrl?: string }
          | undefined;
    
        return {
          id: sub.id,
          type,
          timestamp: attrs.timestamp as string,
          comment: (attrs.comment as string) ?? null,
          testerName: testerAttrs
            ? `${testerAttrs.firstName ?? ""} ${testerAttrs.lastName ?? ""}`.trim() || null
            : null,
          testerEmail: (testerAttrs?.email as string) ?? null,
          buildVersion: buildAttrs?.version ?? null,
          deviceModel: attrs.deviceModel as string,
          osVersion: attrs.osVersion as string,
          locale: attrs.locale as string,
          carrier: (attrs.carrier as string) ?? null,
          timezone: attrs.timezone as string,
          architecture: attrs.architecture as string,
          connectionStatus: attrs.connectionStatus as string,
          batteryPercentage: (attrs.batteryPercentage as number) ?? null,
          appUptime: (attrs.appUptime as number) ?? null,
          screenResolution:
            attrs.screenWidth != null
              ? `${attrs.screenWidth}x${attrs.screenHeight}`
              : null,
          diskSpaceFree: (attrs.diskSpaceFree as number) ?? null,
          screenshotUrl: screenshotAsset?.templateUrl ?? null,
          crashLogUrl:
            type === "crash"
              ? `https://api.appstoreconnect.apple.com/v1/betaFeedbackCrashSubmissions/${sub.id}/relationships/crashLog`
              : null,
        };
      });
    }
  • listIrisFeedback helper: fetches text comment feedback via Apple's internal iris API (requires browser auth).
    export async function listIrisFeedback(
      appId: string,
      options?: { buildId?: string; limit?: number }
    ): Promise<FeedbackItem[] | null> {
      if (!isBrowserEnabled()) return null;
    
      let url = `https://appstoreconnect.apple.com/iris/v1/betaFeedbacks?filter[build.app]=${appId}&sort=-timestamp&exists[crash]=false&include=tester,build,screenshots,buildBundle&fields[betaTesters]=firstName,lastName&fields[builds]=version&limit=${options?.limit ?? 60}`;
    
      if (options?.buildId) {
        url += `&filter[build]=${options.buildId}`;
      }
    
      const response = await fetchWithBrowserAuth(url);
      if (!response) return null;
    
      try {
        const json = (await response.json()) as {
          data: IrisBetaFeedback[];
          included?: JsonApiResource[];
        };
    
        return json.data.map((item) => {
          const testerRef = item.relationships?.tester?.data;
          const buildRef = item.relationships?.build?.data;
          const included = json.included ?? [];
    
          const tester = testerRef
            ? included.find((r) => r.type === "betaTesters" && r.id === testerRef.id)
            : null;
          const build = buildRef
            ? included.find((r) => r.type === "builds" && r.id === buildRef.id)
            : null;
    
          const testerAttrs = tester?.attributes as
            | { firstName?: string; lastName?: string }
            | undefined;
          const buildAttrs = build?.attributes as
            | { version?: string }
            | undefined;
    
          return {
            id: item.id,
            type: "comment" as const,
            timestamp: item.attributes.timestamp,
            comment: item.attributes.comment,
            testerName: testerAttrs
              ? `${testerAttrs.firstName ?? ""} ${testerAttrs.lastName ?? ""}`.trim() || null
              : null,
            testerEmail: item.attributes.emailAddress,
            buildVersion: buildAttrs?.version ?? null,
            deviceModel: item.attributes.deviceModel,
            osVersion: item.attributes.osVersion,
            locale: item.attributes.locale,
            carrier: item.attributes.carrier,
            timezone: item.attributes.timezone,
            architecture: item.attributes.architecture,
            connectionStatus: item.attributes.connectionStatus,
            batteryPercentage: item.attributes.batteryPercentage,
            appUptime: item.attributes.appUptime,
            screenResolution: item.attributes.screenWidth
              ? `${item.attributes.screenWidth}x${item.attributes.screenHeight}`
              : null,
            diskSpaceFree: item.attributes.diskSpaceFree,
            screenshotUrl: null,
            crashLogUrl: null,
          };
        });
      } catch {
        console.error("Failed to parse iris feedback response");
        return null;
      }
    }
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that comments require browser auth, which is valuable. However, it does not explain pagination behavior, rate limits, or whether the operation is read-only (assumed but unstated). Gaps remain in behavioral expectations.

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 main purpose followed by retrieval specifics and filtering options. Every sentence adds value without redundancy.

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 tool has no output schema and the description does not describe the return format or behavior when no results are found. Given the complexity (4 parameters, list tool), additional context on pagination or response structure 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?

The input schema has 100% coverage with descriptions. The description's mention of filtering by build or type reinforces the schema but does not add new meaning beyond what is already in the parameter descriptions. Baseline 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 tool lists TestFlight feedback for an app, specifying the types (screenshots, crashes, comments) and the auth requirement for comments. It distinguishes itself from sibling tools like get_crash_log (specific crash) and get_feedback_detail (single feedback).

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 mentions filtering by build or feedback type, giving clear usage context. However, it does not explicitly state when to avoid this tool in favor of siblings (e.g., for detailed feedback or responding). The absence of exclusions leaves some ambiguity.

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