Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_ci_test_results

Retrieve and filter test results from App Store Connect CI/CD builds to analyze test status, duration, and failures for iOS/macOS development workflows.

Instructions

List test results from a build run or build action

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buildRunIdNoThe ID of the build run to list test results for (provide either buildRunId or buildActionId)
buildActionIdNoThe ID of the build action to list test results for (provide either buildRunId or buildActionId)
limitNoMaximum number of test results to return (default: 100, max: 200)
sortNoSort order for the results
filterNo
includeNoRelated resources to include in the response
fieldsNo

Implementation Reference

  • The handler function listTestResults that executes the core logic: constructs API parameters and calls the App Store Connect API endpoint for CI test results.
    async listTestResults(args: {
      buildRunId?: string;
      buildActionId?: string;
      limit?: number;
      sort?: CiTestResultSortOptions;
      filter?: CiTestResultFilters;
      fields?: {
        ciTestResults?: CiTestResultFieldOptions[];
      };
      include?: CiTestResultIncludeOptions[];
    }): Promise<CiTestResultsResponse> {
      const { buildRunId, buildActionId, limit = 100, sort, filter, fields, include } = args;
      
      if (!buildRunId && !buildActionId) {
        throw new Error('Either buildRunId or buildActionId must be provided');
      }
    
      const params: Record<string, any> = {
        limit: sanitizeLimit(limit)
      };
    
      if (sort) {
        params.sort = sort;
      }
    
      if (include?.length) {
        params.include = include.join(',');
      }
    
      Object.assign(params, buildFilterParams(filter));
      Object.assign(params, buildFieldParams(fields));
    
      const endpoint = buildRunId 
        ? `/ciBuildRuns/${buildRunId}/testResults`
        : `/ciBuildActions/${buildActionId}/testResults`;
    
      return this.client.get<CiTestResultsResponse>(endpoint, params);
    }
  • Tool schema definition including name, description, and detailed inputSchema with parameters for filtering, sorting, and including related data.
      name: "list_ci_test_results",
      description: "List test results from a build run or build action",
      inputSchema: {
        type: "object",
        properties: {
          buildRunId: {
            type: "string",
            description: "The ID of the build run to list test results for (provide either buildRunId or buildActionId)"
          },
          buildActionId: {
            type: "string",
            description: "The ID of the build action to list test results for (provide either buildRunId or buildActionId)"
          },
          limit: {
            type: "number",
            description: "Maximum number of test results to return (default: 100, max: 200)",
            minimum: 1,
            maximum: 200
          },
          sort: {
            type: "string",
            description: "Sort order for the results",
            enum: ["className", "-className", "name", "-name", "status", "-status", "duration", "-duration"]
          },
          filter: {
            type: "object",
            properties: {
              status: {
                type: "string",
                enum: ["SUCCESS", "FAILURE", "SKIPPED"],
                description: "Filter by test status"
              },
              className: {
                type: "string",
                description: "Filter by test class name"
              },
              name: {
                type: "string",
                description: "Filter by test name"
              }
            }
          },
          include: {
            type: "array",
            items: {
              type: "string",
              enum: ["buildAction", "buildRun"]
            },
            description: "Related resources to include in the response"
          },
          fields: {
            type: "object",
            properties: {
              ciTestResults: {
                type: "array",
                items: {
                  type: "string",
                  enum: ["className", "name", "status", "fileLocation", "failureMessage", "duration"]
                },
                description: "Fields to include for each test result"
              }
            }
          }
        }
      }
    }
  • src/index.ts:1446-1448 (registration)
    Registers the tool by mapping the 'list_ci_test_results' name in the switch statement to call the workflowHandlers.listTestResults method.
    case "list_ci_test_results":
      const testResultsData = await this.workflowHandlers.listTestResults(args as any);
      return formatResponse(testResultsData);
  • TypeScript interfaces and types defining the CiTestResultsResponse structure, filters, sort options, fields, and includes used by the tool.
    export interface CiTestResultsResponse {
      data: CiTestResult[];
      included?: Array<{
        id: string;
        type: "ciBuildActions" | "ciBuildRuns";
        attributes: any;
      }>;
      links?: {
        self: string;
        first?: string;
        next?: string;
      };
      meta?: {
        paging: {
          total: number;
          limit: number;
        };
      };
    }
    
    export interface CiTestResultFilters {
      status?: "SUCCESS" | "FAILURE" | "SKIPPED";
      className?: string;
      name?: string;
    }
    
    export type CiTestResultSortOptions = 
      | "className" | "-className"
      | "name" | "-name"
      | "status" | "-status"
      | "duration" | "-duration";
    
    export type CiTestResultFieldOptions = 
      | "className"
      | "name"
      | "status"
      | "fileLocation"
      | "failureMessage"
      | "duration";
    
    export type CiTestResultIncludeOptions =
      | "buildAction"
      | "buildRun";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states it 'lists' test results, implying a read-only operation, but doesn't cover pagination (though 'limit' in schema helps), rate limits, authentication needs, error conditions, or what the response structure looks like. For a tool with 7 parameters and no annotations, this is inadequate.

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 a single, efficient sentence that front-loads the core purpose ('List test results') without unnecessary words. It's appropriately sized for a listing tool, with zero wasted text, making it easy for an agent to parse quickly.

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?

Given the tool's complexity (7 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It lacks details on behavioral traits (e.g., pagination, errors), output format, or usage context. While the schema covers many parameters, the description doesn't compensate for the gaps in behavioral transparency or provide enough guidance for effective tool selection.

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 description mentions 'from a build run or build action', which aligns with the 'buildRunId' and 'buildActionId' parameters in the schema, adding some context. However, with 71% schema description coverage, the schema already documents most parameters well (e.g., 'limit', 'sort', 'filter', 'include', 'fields'). The description doesn't add significant meaning beyond what the schema provides, such as explaining parameter interactions or use cases.

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 action ('List test results') and the resource source ('from a build run or build action'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'list_ci_build_actions' or 'list_build_runs', which list different resources rather than test results specifically.

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. It doesn't mention prerequisites (e.g., needing a build run/action ID), compare it to similar tools (like 'list_ci_issues' for issues vs. test results), or specify scenarios where it's appropriate. The input schema hints at alternatives via 'provide either buildRunId or buildActionId', but this isn't stated in the description itself.

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