Skip to main content
Glama
concavegit

App Store Connect MCP Server

by concavegit

list_workflows

Retrieve App Store Connect CI/CD workflows and their associated apps to manage continuous integration products for iOS, macOS, tvOS, and visionOS development.

Instructions

List all App Store Connect workflows (CI products) and their associated apps

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of workflows to return (default: 100, max: 200)
sortNoSort order for the results
filterNo
includeNoRelated resources to include in the response
fieldsNo

Implementation Reference

  • The core handler function `listWorkflows` in the `WorkflowHandlers` class that implements the tool logic by querying the App Store Connect API endpoint `/ciProducts` with sanitized parameters.
    async listWorkflows(args: {
      limit?: number;
      sort?: CiProductSortOptions;
      filter?: CiProductFilters;
      fields?: {
        ciProducts?: CiProductFieldOptions[];
      };
      include?: CiProductIncludeOptions[];
    } = {}): Promise<CiProductsResponse> {
      const { limit = 100, sort, filter, fields, include } = args;
      
      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));
    
      return this.client.get<CiProductsResponse>('/ciProducts', params);
    }
  • src/index.ts:1423-1425 (registration)
    Registration of the tool handler in the MCP server's `CallToolRequestSchema` handler switch statement, mapping 'list_workflows' calls to `workflowHandlers.listWorkflows`.
    case "list_workflows":
      const workflowsData = await this.workflowHandlers.listWorkflows(args as any);
      return formatResponse(workflowsData);
  • MCP tool metadata and input schema definition for 'list_workflows' returned in the tools list response.
      name: "list_workflows",
      description: "List all App Store Connect workflows (CI products) and their associated apps",
      inputSchema: {
        type: "object",
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of workflows to return (default: 100, max: 200)",
            minimum: 1,
            maximum: 200
          },
          sort: {
            type: "string",
            description: "Sort order for the results",
            enum: ["name", "-name", "productType", "-productType"]
          },
          filter: {
            type: "object",
            properties: {
              productType: {
                type: "string",
                description: "Filter by product type",
                enum: ["IOS", "MAC_OS", "TV_OS", "VISION_OS"]
              }
            }
          },
          include: {
            type: "array",
            items: {
              type: "string",
              enum: ["app", "bundleId", "primaryRepositories"]
            },
            description: "Related resources to include in the response"
          },
          fields: {
            type: "object",
            properties: {
              ciProducts: {
                type: "array",
                items: {
                  type: "string",
                  enum: ["name", "productType"]
                },
                description: "Fields to include for each workflow"
              }
            }
          }
        }
      }
    },
  • TypeScript type definitions for the response and parameters used in the listWorkflows handler (CiProductsResponse, CiProductFilters, etc.).
    export interface CiProductsResponse {
      data: CiProduct[];
      included?: Array<{
        id: string;
        type: "apps" | "bundleIds" | "scmRepositories";
        attributes: any;
      }>;
      links?: {
        self: string;
        first?: string;
        next?: string;
      };
      meta?: {
        paging: {
          total: number;
          limit: number;
        };
      };
    }
    
    export interface CiProductFilters {
      productType?: CiProductType;
    }
    
    export type CiProductSortOptions = 
      | "name" | "-name"
      | "productType" | "-productType";
    
    export type CiProductFieldOptions = 
      | "name"
      | "productType";
    
    export type CiProductIncludeOptions =
      | "app"
      | "bundleId" 
      | "primaryRepositories";
    
    // Build Run Types
    export interface CiBuildRun {
      id: string;
      type: "ciBuildRuns";
      attributes: {
        number: number;
  • src/index.ts:82-82 (registration)
    Instantiation of the WorkflowHandlers class instance used for the workflows tools.
    this.workflowHandlers = new WorkflowHandlers(this.client);
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. It only states what the tool does ('List all...') without mentioning permissions, rate limits, pagination, response format, or error handling. For a tool with 5 parameters and no output schema, this leaves critical behavioral traits undocumented.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy 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 complexity (5 parameters, nested objects, no output schema, and no annotations), the description is incomplete. It lacks details on behavioral traits, parameter usage, and response handling, making it inadequate for an agent to fully understand how to invoke and interpret results from this tool.

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 adds no parameter-specific information beyond what's in the input schema. With 60% schema description coverage (3 out of 5 parameters have descriptions), the baseline is 3, as the schema does moderate lifting but the description doesn't compensate for gaps like the 'filter' or 'fields' object details.

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 ('App Store Connect workflows (CI products) and their associated apps'), making the purpose specific and understandable. However, it doesn't differentiate from sibling tools like 'list_apps' or 'list_build_runs', which also list resources in the same domain, so it doesn't fully distinguish itself from alternatives.

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, context, or compare to sibling tools like 'list_apps' or 'list_build_runs', leaving the agent with no usage direction beyond the basic purpose.

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