Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_ci_issues

Retrieve and filter CI/CD build issues and errors from App Store Connect to identify and resolve problems in iOS/macOS development workflows.

Instructions

List issues and errors from a build run or build action

Input Schema

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

Implementation Reference

  • The `listIssues` method in WorkflowHandlers class that executes the core logic of the 'list_ci_issues' tool. It validates input, builds query parameters using helpers, determines the appropriate App Store Connect API endpoint (/ciBuildRuns/{id}/issues or /ciBuildActions/{id}/issues), and fetches the issues data via the client.
    async listIssues(args) {
        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 = {
            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}/issues`
            : `/ciBuildActions/${buildActionId}/issues`;
        return this.client.get(endpoint, params);
    }
  • Input schema and metadata definition for the 'list_ci_issues' tool, provided to the MCP server for tool listing and validation.
        name: "list_ci_issues",
        description: "List issues and errors from a build run or build action",
        inputSchema: {
            type: "object",
            properties: {
                buildRunId: {
                    type: "string",
                    description: "The ID of the build run to list issues for (provide either buildRunId or buildActionId)"
                },
                buildActionId: {
                    type: "string",
                    description: "The ID of the build action to list issues for (provide either buildRunId or buildActionId)"
                },
                limit: {
                    type: "number",
                    description: "Maximum number of issues to return (default: 100, max: 200)",
                    minimum: 1,
                    maximum: 200
                },
                sort: {
                    type: "string",
                    description: "Sort order for the results",
                    enum: ["issueType", "-issueType", "category", "-category", "message", "-message"]
                },
                filter: {
                    type: "object",
                    properties: {
                        issueType: {
                            type: "string",
                            enum: ["ANALYZER_WARNING", "ERROR", "TEST_FAILURE", "WARNING"],
                            description: "Filter by issue type"
                        },
                        category: {
                            type: "string",
                            description: "Filter by issue category"
                        }
                    }
                },
                include: {
                    type: "array",
                    items: {
                        type: "string",
                        enum: ["buildAction", "buildRun"]
                    },
                    description: "Related resources to include in the response"
                },
                fields: {
                    type: "object",
                    properties: {
                        ciIssues: {
                            type: "array",
                            items: {
                                type: "string",
                                enum: ["issueType", "message", "fileSource", "category"]
                            },
                            description: "Fields to include for each issue"
                        }
                    }
                }
            }
        }
    },
    // CI Test Results Management
  • Tool dispatch registration in the MCP CallToolRequestHandler switch statement, mapping 'list_ci_issues' calls to the workflowHandlers.listIssues method and formatting the response.
    case "list_ci_issues":
        const issuesData = await this.workflowHandlers.listIssues(args);
        return formatResponse(issuesData);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states it 'List issues and errors' but doesn't disclose pagination behavior (though schema implies limit/default), rate limits, authentication needs, or what happens with missing IDs. It lacks context on response format, error handling, or whether it's read-only/destructive.

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. Every word earns its place with no redundancy or fluff. It's appropriately sized for a list operation tool.

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 7 parameters, no annotations, no output schema, and nested objects, the description is incomplete. It doesn't address complexity like filter/fields usage, response structure, or error cases. For a tool with rich input options and no structured output documentation, more guidance is needed.

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 71%, so the schema documents most parameters well. The description adds no parameter-specific semantics beyond implying 'build run or build action' context for IDs. It doesn't explain parameter interactions, defaults beyond schema, or usage examples. Baseline 3 is appropriate given schema does 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 ('issues and errors'), specifying they come from 'a build run or build action'. It distinguishes from siblings like 'list_ci_test_results' by focusing on issues/errors rather than test results. However, it doesn't explicitly differentiate from all sibling tools, just implies scope.

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 is provided. The description doesn't mention prerequisites, when-not scenarios, or compare with similar tools like 'list_ci_test_results'. The input schema hints at alternatives with 'provide either buildRunId or buildActionId', but the description itself offers no usage context.

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