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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ci_products_get_collection

List Xcode Cloud CI products with optional filters for app or product type, and include related apps, bundle IDs, or repositories.

Instructions

GET /v1/ciProducts (GET /v1/ciProducts)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNomaximum resources per page
includeNocomma-separated list of relationships to include
filter_appNofilter by id(s) of related 'app'
fields_appsNothe fields to include for returned resources of type apps
fields_bundleIdsNothe fields to include for returned resources of type bundleIds
fields_ciProductsNothe fields to include for returned resources of type ciProducts
filter_productTypeNofilter by attribute 'productType'
fields_scmRepositoriesNothe fields to include for returned resources of type scmRepositories
limit_primaryRepositoriesNomaximum number of related primaryRepositories returned (when they are included)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden, and it does almost nothing. The "GET" verb implies a safe read, but there is no mention of pagination (despite limit/limit_primaryRepositories params), filtering behavior, auth requirements, or result shape.

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 description is extremely short, but here brevity reflects under-specification rather than discipline. It adds no front-loaded clarifying information, so it does not earn its place as a description.

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?

For a 9-parameter collection endpoint with no annotations and no output schema, an agent needs at minimum to know what a CI product is, how paging/filtering behaves, and how it relates to sibling resources. None of that is present.

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% across all 9 parameters, so the schema fully documents limit, include, filter_app, the fields_* selectors and filter_productType. The description adds nothing beyond the schema, which sets the baseline at 3.

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 a verified HTTP path ("GET /v1/ciProducts (GET /v1/ciProducts)") that restates the tool name in URL form. It conveys that this is a read/list of CI products only because the name and path imply it, not through any explanatory verb+resource statement.

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 when-to-use guidance, no mention of alternatives such as ci_products_get_instance, ci_products_workflows_get_to_many_related, or ci_products_build_runs_get_to_many_related, and no exclusions of any kind.

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