Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

list_builds

Retrieve TestFlight builds for your app. Filter by version or processing state to view build numbers, upload dates, and statuses.

Instructions

List TestFlight builds for an app. Filter by version or processing state. Returns build number, version, upload date, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
app_idYesApp Store Connect app ID
versionNoFilter by pre-release version string (e.g., '1.2.0')
processing_stateNoFilter by build processing state
limitNoMaximum number of builds to return (default: 20)

Implementation Reference

  • The main handler function for the list_builds tool. Takes a validated schema input, calls the API's listBuilds function, and maps the response to a simplified output format with build number, version, platform, upload date, processing state, expiry, and min OS version.
    export async function handleListBuilds(
      client: AppStoreConnectClient,
      args: z.infer<typeof listBuildsSchema>
    ) {
      const { builds, included } = await listBuilds(client, {
        appId: args.app_id,
        preReleaseVersion: args.version,
        processingState: args.processing_state,
        limit: args.limit,
      });
    
      return builds.map((build) => {
        const versionRef = build.relationships?.preReleaseVersion?.data;
        const versionResource =
          versionRef && !Array.isArray(versionRef)
            ? included.find(
                (r) => r.type === "preReleaseVersions" && r.id === versionRef.id
              )
            : null;
        const versionAttrs = versionResource?.attributes as
          | { version?: string; platform?: string }
          | undefined;
    
        return {
          id: build.id,
          buildNumber: build.attributes.version,
          appVersion: versionAttrs?.version ?? null,
          platform: versionAttrs?.platform ?? null,
          uploadedDate: build.attributes.uploadedDate,
          processingState: build.attributes.processingState,
          expired: build.attributes.expired,
          minOsVersion: build.attributes.minOsVersion,
        };
      });
    }
  • Zod schema defining the input parameters for list_builds: app_id (required string), version (optional string for pre-release filtering), processing_state (optional enum), and limit (optional number 1-200).
    export const listBuildsSchema = z.object({
      app_id: z.string().describe("App Store Connect app ID"),
      version: z
        .string()
        .optional()
        .describe("Filter by pre-release version string (e.g., '1.2.0')"),
      processing_state: z
        .enum(["PROCESSING", "FAILED", "INVALID", "VALID"])
        .optional()
        .describe("Filter by build processing state"),
      limit: z
        .number()
        .min(1)
        .max(200)
        .optional()
        .describe("Maximum number of builds to return (default: 20)"),
    });
  • src/index.ts:52-62 (registration)
    Registration of the 'list_builds' tool on the MCP server with its schema and handler, wiring it into the server's tool registry.
    server.tool(
      "list_builds",
      "List TestFlight builds for an app. Filter by version or processing state. Returns build number, version, upload date, and status.",
      listBuildsSchema.shape,
      async (args) => {
        const result = await handleListBuilds(client, args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • API helper function that constructs App Store Connect API query parameters and calls the /builds endpoint via the client. Handles filtering by app, pre-release version, processing state, and sorting.
    export async function listBuilds(
      client: AppStoreConnectClient,
      options: ListBuildsOptions
    ): Promise<{ builds: Build[]; included: JsonApiResource[] }> {
      const params: Record<string, string> = {
        "filter[app]": options.appId,
        "fields[builds]":
          "version,uploadedDate,expirationDate,expired,minOsVersion,processingState,buildAudienceType",
        include: "preReleaseVersion",
        "fields[preReleaseVersions]": "version,platform",
        limit: String(options.limit ?? 20),
        sort: options.sort ?? "-uploadedDate",
      };
    
      if (options.preReleaseVersion) {
        params["filter[preReleaseVersion.version]"] = options.preReleaseVersion;
      }
      if (options.processingState) {
        params["filter[processingState]"] = options.processingState;
      }
    
      const response = await client.requestAll<Build>("/builds", params);
      return { builds: response.data, included: response.included };
    }
  • TypeScript interface defining the options passed to the API-level listBuilds function.
    export interface ListBuildsOptions {
      appId: string;
      limit?: number;
      preReleaseVersion?: string;
      processingState?: "PROCESSING" | "FAILED" | "INVALID" | "VALID";
      sort?: string;
    }
Behavior3/5

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

With no annotations, the description carries the burden. It specifies return fields (build number, version, upload date, status) and filtering, but lacks details on pagination, sorting, or side effects. It does not explicitly declare the tool as read-only.

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 totaling 16 words, front-loaded with the core purpose, followed by filtering and return values. Every sentence is essential and efficient.

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?

Given no output schema and 4 parameters, the description covers the main purpose and return fields. It omits details about the limit parameter's default and error handling, but is largely adequate for a simple list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds value by summarizing the filtering ('Filter by version or processing state') and listing the return fields, which are not in the schema.

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 ('List'), resource ('TestFlight builds'), and scope ('for an app'). It also mentions filtering capabilities, and the tool's purpose is distinct from siblings like list_apps or 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 Guidelines3/5

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

The description implies when to use the tool (to list builds), but it does not explicitly state when not to use it or provide alternatives. No exclusions or context versus other list tools is given.

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