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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ci_build_actions_issues_get_to_many_related

Retrieve paginated issues for a specific Xcode Cloud CI build action to inspect build failures and related problems.

Instructions

GET /v1/ciBuildActions/{id}/issues (GET /v1/ciBuildActions/{id}/issues)

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_build_actions_issues_get_to_many_related"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page
fields_ciIssuesNothe fields to include for returned resources of type ciIssues

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing. The 'GET' verb weakly implies a read-only operation, but there is no mention of pagination behavior despite a 'limit' parameter, no auth/permission requirements, and no note on what is returned or whether results may be empty for a build action with no issues.

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?

It is short, but the brevity comes from having no content at all, and the path is duplicated verbatim inside parentheses. Nothing is front-loaded because there is nothing substantive to front-load.

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 related-list endpoint with three parameters, no annotations, and no output schema, the description should at least explain the relationship and the pagination/sparse-field options. Instead it provides only a URL, leaving the agent unable to confidently distinguish this tool from the many similar get-to-many siblings.

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%, so the schema already documents 'id', 'limit', and 'fields_ciIssues'. The description adds no additional meaning about parameter usage or sparsity semantics. Baseline 3 applies when the schema does the heavy lifting.

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 the raw HTTP path repeated twice: 'GET /v1/ciBuildActions/{id}/issues (GET /v1/ciBuildActions/{id}/issues)'. It restates the tool name rather than describing intent, though the path does hint that it lists CI issues attached to a build action. No distinction from siblings such as ci_build_actions_issues_get_to_many_relationship or ci_issues_get_instance.

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?

There is no statement of when to call this tool, what alternative to use for a single issue (ci_issues_get_instance), or what the 'to_many_related' semantics mean relative to the corresponding '_relationship' sibling. The agent must infer everything from the URL.

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