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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_group_versions_localizations_get_to_many_relationship

Retrieve the localization relationship data for a subscription group version to see which App Store localizations are linked when managing subscriptions.

Instructions

GET /v1/subscriptionGroupVersions/{id}/relationships/localizations (GET /v1/subscriptionGroupVersions/{id}/relationships/localizations)

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page

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 burden. The 'GET' prefix weakly implies a read operation, but nothing is said about pagination behavior despite a limit parameter, about what the relationship linkage returns, or about auth requirements. For an unannotated tool this is a substantial gap.

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 repeats the identical path string verbatim, which is pure redundancy rather than conciseness. There is no front-loaded purpose statement, only a raw URL.

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?

The operation is low-complexity (a to-many relationship read, 2 params, full schema coverage, no output schema), so the bar is modest, but the description still omits any indication of what a 'relationship' endpoint returns and how it differs from the '_related' sibling, leaving the agent to guess.

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% (id and limit are both documented in the schema), so the baseline is 3. The description adds no syntax, format, or meaning beyond what the schema already states, but it does not need to compensate for any coverage gap.

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 a bare restatement of the HTTP path and duplicates it verbatim in parentheses: 'GET /v1/subscriptionGroupVersions/{id}/relationships/localizations (GET ...)'. It names a verb and a resource, so it is not meaningless, but it is a tautology of the tool name with no natural-language statement of what the operation returns or why an agent would call it over the sibling *_get_to_many_related variant.

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 when-to-use guidance, no distinction from the nearly identical 'subscription_group_versions_localizations_get_to_many_related' sibling, and no prerequisites. The only implicit signal is the 'relationship' suffix versus the 'related' sibling, which the description never explains.

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