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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_group_localizations_get_instance

Retrieve a subscription group localization by ID from App Store Connect, with optional relationship includes and field selection for subscription groups or localizations.

Instructions

GET /v1/subscriptionGroupLocalizations/{id} (GET /v1/subscriptionGroupLocalizations/{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": "subscription_group_localizations_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_subscriptionGroupsNothe fields to include for returned resources of type subscriptionGroups
fields_subscriptionGroupLocalizationsNothe fields to include for returned resources of type subscriptionGroupLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.1/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it only reveals that the operation is a GET. It says nothing about authentication, whether the response is a single resource, error behavior for a missing id, or what the include/fields expansions actually do.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but half of it is a pure duplicate of the other half, which is wasted space. It is front-loaded only in the sense that there is nothing 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 four-parameter read tool with no annotations and no output schema, the description says nothing about the returned resource shape, the effect of the include/fields parameters, or expected failure modes. It is far short of what an agent needs to call this correctly on first attempt.

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 all four parameters (id, include, fields_subscriptionGroups, fields_subscriptionGroupLocalizations) are documented in the schema itself. The description adds nothing beyond naming {id} in the path, so the baseline of 3 applies; no compensation was needed but no value was added.

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 essentially the tool name restated as a raw path: "GET /v1/subscriptionGroupLocalizations/{id} (GET /v1/subscriptionGroupLocalizations/{id})". It implies fetching one localization resource, but the parenthetical duplicates the same string and no plain-language statement of intent is given; it does not distinguish this from subscription_group_localizations_v2_get_instance or the collection/get_instance siblings.

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?

No when-to-use, prerequisites, or alternative routing is provided. An agent cannot tell from this text why it would call this rather than the v2 variant or the to-many relationship tool on subscription_groups.

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