Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_beta_feedback_screenshots

Retrieve beta feedback screenshots with device details and tester comments for app testing analysis. Filter by build, platform, device, OS version, or tester to identify issues.

Instructions

List all beta feedback screenshot submissions for an app. This includes feedback with screenshots, device information, and tester comments. You can identify the app using either appId or bundleId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNoThe ID of the app to get feedback for (e.g., '6747745091')
bundleIdNoThe bundle ID of the app (e.g., 'com.example.app'). Can be used instead of appId.
buildIdNoFilter by specific build ID (optional)
devicePlatformNoFilter by device platform (optional)
appPlatformNoFilter by app platform (optional)
deviceModelNoFilter by device model (e.g., 'iPhone15_2') (optional)
osVersionNoFilter by OS version (e.g., '18.4.1') (optional)
testerIdNoFilter by specific tester ID (optional)
limitNoMaximum number of feedback items to return (default: 50, max: 200)
sortNoSort order for results (default: -createdDate for newest first)
includeBuildsNoInclude build information in response (optional)
includeTestersNoInclude tester information in response (optional)

Implementation Reference

  • The handler function that executes the tool: fetches beta feedback screenshot submissions from App Store Connect API with filtering, sorting, and optional includes.
    async listBetaFeedbackScreenshots(args: ListBetaFeedbackScreenshotSubmissionsRequest): Promise<ListBetaFeedbackScreenshotSubmissionsResponse> {
      const { 
        appId, 
        bundleId,
        buildId,
        devicePlatform,
        appPlatform,
        deviceModel,
        osVersion,
        testerId,
        limit = 50,
        sort = "-createdDate",
        includeBuilds = false,
        includeTesters = false
      } = args;
      
      // Require either appId or bundleId
      if (!appId && !bundleId) {
        throw new Error('Either appId or bundleId must be provided');
      }
      
      // If bundleId is provided but not appId, look up the app
      let finalAppId = appId;
      if (!appId && bundleId) {
        const app = await this.appHandlers.findAppByBundleId(bundleId);
        if (!app) {
          throw new Error(`No app found with bundle ID: ${bundleId}`);
        }
        finalAppId = app.id;
      }
    
      // Build query parameters
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit),
        sort
      };
    
      // Add filters if provided
      if (buildId) {
        params['filter[build]'] = buildId;
      }
      if (devicePlatform) {
        params['filter[devicePlatform]'] = devicePlatform;
      }
      if (appPlatform) {
        params['filter[appPlatform]'] = appPlatform;
      }
      if (deviceModel) {
        params['filter[deviceModel]'] = deviceModel;
      }
      if (osVersion) {
        params['filter[osVersion]'] = osVersion;
      }
      if (testerId) {
        params['filter[tester]'] = testerId;
      }
    
      // Add includes if requested
      const includes: string[] = [];
      if (includeBuilds) includes.push('build');
      if (includeTesters) includes.push('tester');
      if (includes.length > 0) {
        params.include = includes.join(',');
      }
    
      // Add field selections for better performance
      params['fields[betaFeedbackScreenshotSubmissions]'] = 'createdDate,comment,email,deviceModel,osVersion,locale,timeZone,architecture,connectionType,pairedAppleWatch,appUptimeInMilliseconds,diskBytesAvailable,diskBytesTotal,batteryPercentage,screenWidthInPoints,screenHeightInPoints,appPlatform,devicePlatform,deviceFamily,buildBundleId,screenshots,build,tester';
    
      return this.client.get<ListBetaFeedbackScreenshotSubmissionsResponse>(
        `/apps/${finalAppId}/betaFeedbackScreenshotSubmissions`, 
        params
      );
    }
  • src/index.ts:1334-1336 (registration)
    MCP tool registration: switch case that dispatches tool calls to the betaHandlers.listBetaFeedbackScreenshots method.
    case "list_beta_feedback_screenshots":
      const feedbackData = await this.betaHandlers.listBetaFeedbackScreenshots(args as any);
      return formatResponse(feedbackData);
  • MCP tool definition including name, description, and detailed inputSchema for validation.
      name: "list_beta_feedback_screenshots",
      description: "List all beta feedback screenshot submissions for an app. This includes feedback with screenshots, device information, and tester comments. You can identify the app using either appId or bundleId.",
      inputSchema: {
        type: "object",
        properties: {
          appId: {
            type: "string",
            description: "The ID of the app to get feedback for (e.g., '6747745091')"
          },
          bundleId: {
            type: "string",
            description: "The bundle ID of the app (e.g., 'com.example.app'). Can be used instead of appId."
          },
          buildId: {
            type: "string",
            description: "Filter by specific build ID (optional)"
          },
          devicePlatform: {
            type: "string",
            enum: ["IOS", "MAC_OS", "TV_OS", "VISION_OS"],
            description: "Filter by device platform (optional)"
          },
          appPlatform: {
            type: "string",
            enum: ["IOS", "MAC_OS", "TV_OS", "VISION_OS"],
            description: "Filter by app platform (optional)"
          },
          deviceModel: {
            type: "string",
            description: "Filter by device model (e.g., 'iPhone15_2') (optional)"
          },
          osVersion: {
            type: "string",
            description: "Filter by OS version (e.g., '18.4.1') (optional)"
          },
          testerId: {
            type: "string",
            description: "Filter by specific tester ID (optional)"
          },
          limit: {
            type: "number",
            description: "Maximum number of feedback items to return (default: 50, max: 200)",
            minimum: 1,
            maximum: 200
          },
          sort: {
            type: "string",
            enum: ["createdDate", "-createdDate"],
            description: "Sort order for results (default: -createdDate for newest first)"
          },
          includeBuilds: {
            type: "boolean",
            description: "Include build information in response (optional)",
            default: false
          },
          includeTesters: {
            type: "boolean",
            description: "Include tester information in response (optional)",
            default: false
          }
        },
        required: []
      }
    },
  • TypeScript interface defining the input parameters for the handler.
    export interface ListBetaFeedbackScreenshotSubmissionsRequest {
      appId?: string;
      bundleId?: string;
      buildId?: string;
      devicePlatform?: "IOS" | "MAC_OS" | "TV_OS" | "VISION_OS";
      appPlatform?: "IOS" | "MAC_OS" | "TV_OS" | "VISION_OS";
      deviceModel?: string;
      osVersion?: string;
      testerId?: string;
      limit?: number;
      sort?: "createdDate" | "-createdDate";
      includeBuilds?: boolean;
      includeTesters?: boolean;
    }
Behavior2/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 states this is a list operation, implying read-only behavior, but doesn't disclose pagination behavior, rate limits, authentication requirements, or what happens if no feedback exists. The description adds minimal behavioral context beyond the basic 'list' action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that efficiently convey the purpose and key parameter usage. The first sentence states what the tool does and what it includes; the second clarifies the app identification options. No wasted words, though it could be slightly more structured with bullet points for the included content.

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?

For a tool with 12 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return format, pagination, error conditions, or how the optional filters interact. The agent would need to rely heavily on the input schema alone, missing important behavioral context.

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 the schema already documents all 12 parameters thoroughly. The description adds that you can 'identify the app using either appId or bundleId', which clarifies the relationship between these two parameters, but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 resource ('beta feedback screenshot submissions for an app'), and specifies the content includes 'feedback with screenshots, device information, and tester comments'. It doesn't explicitly differentiate from sibling tools like 'get_beta_feedback_screenshot' (singular vs. plural), but the plural 'list all' indicates a collection operation.

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 usage for retrieving beta feedback with screenshots, but doesn't explicitly state when to use this tool versus alternatives like 'get_beta_feedback_screenshot' (singular) or other feedback-related tools. It mentions identifying the app using 'appId or bundleId', which provides some context but no explicit exclusions or comparisons to siblings.

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/concavegit/app-store-connect-mcp-server'

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