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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ci_artifacts_get_instance

Retrieves a specific Xcode Cloud CI artifact by ID, with optional fields for file type, name, size, and download URL.

Instructions

GET /v1/ciArtifacts/{id} (GET /v1/ciArtifacts/{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_artifacts_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
fields_ciArtifactsNothe fields to include for returned resources of type ciArtifacts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.7/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 disclosure burden, and it discloses nothing. The only hint of behavior is the HTTP verb 'GET', which is already implied by the tool name, so there is no added context about auth requirements, error behavior, or what happens with an unknown id.

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 parenthetical duplicates the exact same route string and conveys no additional information, making it pure noise rather than efficiency. There is no front-loaded explanation of purpose or scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and a description that only echoes the route, an agent has no way to know what is returned (file metadata? download links?) or how this differs from the sibling artifact relationship tools. This is completely inadequate for a retrieval tool in a large API surface.

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%: both 'id' and 'fields_ciArtifacts' (with its enum of fileType/fileName/fileSize/downloadUrl) are documented in the schema. The description adds no syntax or format meaning beyond that, so the baseline 3 applies.

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 effectively a restatement of the tool's route: 'GET /v1/ciArtifacts/{id}'. The 'GET' verb and 'ciArtifacts' resource are visible in the name itself, so nothing new is conveyed — no statement of what a CI artifact record actually is or what the call returns. It does not distinguish this from siblings like ci_build_actions_artifacts_get_to_many_relationship or ci_artifacts_get_instance variants.

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 whatsoever on when to use this tool, what prerequisite state is required, or which alternative to choose when the artifact id is unknown. An agent must guess between this and the many other ci_* retrieval tools.

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