Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ci_workflows_get_instance

Retrieve a specific Xcode Cloud CI workflow by its ID from App Store Connect to inspect its configuration, conditions, actions, and related product, repository, or version details.

Instructions

GET /v1/ciWorkflows/{id} (GET /v1/ciWorkflows/{id})

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "ci_workflows_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_ciProductsNothe fields to include for returned resources of type ciProducts
fields_ciWorkflowsNothe fields to include for returned resources of type ciWorkflows
fields_ciMacOsVersionsNothe fields to include for returned resources of type ciMacOsVersions
fields_ciXcodeVersionsNothe fields to include for returned resources of type ciXcodeVersions
fields_scmRepositoriesNothe fields to include for returned resources of type scmRepositories

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about authentication, rate limits, or return behavior. The endpoint string implies a read, but there is no substantive transparency.

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

Conciseness2/5

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

The text is short but wastes half its length duplicating the same endpoint string in parentheses. It is under-specified rather than genuinely concise, and provides no front-loaded purpose statement.

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 get-instance tool with a rich 7-parameter schema and no output schema, the description should at least say it retrieves a single CI workflow and note the include/fields expansion behavior. It supplies neither, leaving the definition near-empty.

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% with 7 documented parameters (id, include, fields_*), so the schema does the heavy lifting. The description adds no parameter meaning beyond what the schema already provides, which is the baseline-3 case.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is just the raw endpoint path 'GET /v1/ciWorkflows/{id}', repeated verbatim in parentheses. It restates the tool name in URL form rather than stating in prose what the tool does, and offers no differentiation from the many sibling get_instance tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as ci_workflows_build_runs_get_to_many_related, ci_workflows_repository_get_to_one_related, or ci_workflows_update_instance. No context or prerequisites are given.

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

Deploy Server

Other Tools