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
      );
    }
  • 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;
    }

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided; description only states basic functionality without disclosing behavioral traits such as read-only nature, pagination, or authorization needs.

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, directly to the point, no unnecessary words or repetition.

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?

With 12 parameters and no output schema, description lacks explanation of result structure, pagination, or overall behavior beyond listing.

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 has 100% coverage, so baseline 3; description adds minimal value by indicating appId and bundleId are alternatives, but does not elaborate on other parameters.

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?

Description clearly states the verb 'List' and the resource 'beta feedback screenshot submissions', and distinguishes from sibling tool 'get_beta_feedback_screenshot' by explicitly mentioning 'List all'.

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, nor any exclusionary or contextual direction for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.