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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_localizations_v2_get_instance

Retrieves a specific subscription localization by ID from App Store Connect, letting you include related version data and select returned fields for localization or version details.

Instructions

GET /v2/subscriptionLocalizations/{id} (GET /v2/subscriptionLocalizations/{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_localizations_v2_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_subscriptionVersionsNothe fields to include for returned resources of type subscriptionVersions
fields_subscriptionLocalizationsNothe fields to include for returned resources of type subscriptionLocalizations

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 behavioral burden, and it delivers nothing: no statement about idempotency, permissions, what the response contains, or how sparse fieldsets/include behave. The endpoint path alone discloses nothing an agent cannot infer from the name.

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 text is short, which is good, but the entire second half is a pointless verbatim duplication of the path in parentheses. Every character here fails the 'earns its place' test since it conveys zero additional information.

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 4-parameter retrieval tool with no annotations and no output schema, the description should explain what resource is returned and how the sparse-fieldset parameters behave. It provides none of that, and the sibling set is far too crowded for a bare endpoint string to be sufficient context.

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, include, fields_subscriptionVersions, fields_subscriptionLocalizations all documented in the schema), so the structured field already does the work and the baseline is 3. The description adds no semantics on top of the schema, but no gap is left unaddressed either.

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 a restatement of the tool name/path: 'GET /v2/subscriptionLocalizations/{id}', duplicated verbatim in parentheses. It implies retrieval of a subscription localization by id, but adds no vocabulary that distinguishes it from the many sibling get_instance tools (e.g., subscription_localizations_get_instance, subscription_group_localizations_v2_get_instance).

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 about when to use this tool versus alternatives. With dozens of sibling localization retrieval tools (subscription_localizations_get_instance, subscription_localizations_v2_* family, subscriptions_subscription_localizations_get_to_many_relationship), an agent gets no signal for choosing this one.

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