Skip to main content
Glama
BandaruDheeraj

TestFlight Feedback MCP Server

list_apps

Retrieve a list of all apps in your App Store Connect account, including app ID, name, bundle ID, and SKU.

Instructions

List all apps in your App Store Connect account. Returns app ID, name, bundle ID, and SKU.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of apps to return (default: 50)

Implementation Reference

  • The main handler function for the list_apps tool. Calls the API helper and maps the response to a simplified format (id, name, bundleId, sku, primaryLocale).
    export async function handleListApps(
      client: AppStoreConnectClient,
      args: z.infer<typeof listAppsSchema>
    ) {
      const apps = await listApps(client, { limit: args.limit });
      return apps.map((app) => ({
        id: app.id,
        name: app.attributes.name,
        bundleId: app.attributes.bundleId,
        sku: app.attributes.sku,
        primaryLocale: app.attributes.primaryLocale,
      }));
    }
  • Zod schema for list_apps input validation. Accepts an optional 'limit' parameter (1-200, default 50).
    export const listAppsSchema = z.object({
      limit: z
        .number()
        .min(1)
        .max(200)
        .optional()
        .describe("Maximum number of apps to return (default: 50)"),
    });
  • src/index.ts:40-50 (registration)
    Registration of the 'list_apps' tool on the MCP server with its schema, description, and handler callback.
    server.tool(
      "list_apps",
      "List all apps in your App Store Connect account. Returns app ID, name, bundle ID, and SKU.",
      listAppsSchema.shape,
      async (args) => {
        const result = await handleListApps(client, args);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • API helper function that calls the App Store Connect API endpoint /apps with pagination support via client.requestAll, requesting name, bundleId, sku, primaryLocale fields.
    export async function listApps(
      client: AppStoreConnectClient,
      options?: { limit?: number }
    ): Promise<App[]> {
      const params: Record<string, string> = {
        "fields[apps]": "name,bundleId,sku,primaryLocale",
        limit: String(options?.limit ?? 50),
      };
    
      const response = await client.requestAll<App>("/apps", params);
      return response.data;
    }
  • TypeScript type definitions: AppAttributes (name, bundleId, sku, primaryLocale) and the App interface used by the list_apps tool.
    export interface AppAttributes {
      name: string;
      bundleId: string;
      sku: string;
      primaryLocale: string;
    }
    
    export interface App extends JsonApiResource {
      type: "apps";
      attributes: AppAttributes;
    }
Behavior2/5

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

With no annotations, the description carries the full burden. It claims to 'list all apps' but the limit parameter (default 50, max 200) implies it may not return all apps. This contradiction and lack of pagination details reduce transparency.

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 concise with two sentences: one for action and one for return fields. Every word adds value, and the structure is front-loaded with the primary purpose.

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?

While the description states the return fields, it omits details about the limit parameter and pagination behavior. For a simple tool without an output schema, this is adequate but not fully complete.

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% description coverage for the limit parameter, so the baseline is 3. The description does not add any additional meaning to the parameter beyond the schema, thus earning the baseline score.

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 verb 'List' and the resource 'apps in your App Store Connect account', and distinguishes it from sibling tools like list_beta_groups and list_builds. It also specifies the return fields (app ID, name, bundle ID, SKU), making the purpose very clear.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when to use list_builds for app-specific builds. There is no mention of prerequisites, filtering, or limitations like pagination.

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