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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

alternative_distribution_domains_get_collection

Retrieve a paginated list of alternative distribution domains from App Store Connect to inspect or manage domains for alternative app distribution. Choose fields to include in the response.

Instructions

GET /v1/alternativeDistributionDomains (GET /v1/alternativeDistributionDomains)

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": "alternative_distribution_domains_get_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomaximum resources per page
fields_alternativeDistributionDomainsNothe fields to include for returned resources of type alternativeDistributionDomains

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?

No annotations are provided, so the description carries the full behavioral burden, and it discharges almost none of it. The embedded "GET" verb weakly implies a read-only, non-destructive operation, but there is no mention of pagination behavior (despite a limit parameter), authentication requirements, or the shape of the returned collection.

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 single line is short but wastes its only content on restating the same path twice, which is pure redundancy rather than concision. It is under-specified rather than appropriately sized, leaving almost no useful signal.

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 list-collection endpoint with no output schema and no annotations, the description should convey scope (all domains, not one), pagination, and the read-only nature. None of that is present, so an agent must rely entirely on the schema and sibling naming to call it correctly.

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 the limit and fields_alternativeDistributionDomains parameters are documented in the schema itself. The description adds no parameter detail whatsoever, so the baseline of 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 just the HTTP path repeated twice in parentheses: "GET /v1/alternativeDistributionDomains (GET /v1/alternativeDistributionDomains)". It restates the tool name rather than stating in plain language that it lists/retrieves all alternative distribution domains. An agent can infer the resource from the path, but this is tautological rather than a clear purpose statement.

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 guidance on when to use this collection endpoint versus the sibling alternative_distribution_domains_get_instance, alternative_distribution_domains_create_instance, or alternative_distribution_domains_delete_instance. No prerequisites, no scope, no alternatives are named.

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