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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_localizations_get_instance

Retrieve a subscription localization by ID to access its locale, name, description, state, and optional related subscription details for App Store Connect.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_subscriptionsNothe fields to include for returned resources of type subscriptions
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

C2/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, and it discloses almost nothing. The 'GET' prefix weakly implies a read-only fetch, but that merely echoes the tool name; there is no mention of authentication needs, error behavior for invalid IDs, or whether the include/fields parameters alter the payload 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?

It is short, but not concise in a useful sense: the entire content is the identical endpoint string repeated twice in parentheses, which is pure redundancy with zero informational payload. There is no front-loaded statement of purpose to earn the space.

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 instance-fetch tool with no output schema and no annotations, the description should at minimum explain what the resource represents and what the include/fields parameters affect. It supplies none of that; only the input schema prevents this from being uncallable.

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%, with 'id', 'include', and both 'fields_*' parameters fully documented in the schema, so the baseline is 3. The description adds no syntax, defaults, or format hints beyond what the schema already provides.

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 verbatim restatement of the endpoint URL, duplicated in parentheses, with no explanation of what a 'subscription localization' resource actually is. The GET verb does indicate retrieval, but the text is functionally a tautology of the tool name and gives no way to distinguish it from subscription_localizations_v2_get_instance or subscriptions_subscription_localizations_get_to_many_related.

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 whatsoever. Nothing tells the agent when to fetch a subscription localization directly versus via a relationship or collection endpoint, and no prerequisites or context are stated.

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