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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_localizations_create_instance

Create localized names and descriptions for auto-renewable subscriptions in App Store Connect, so each storefront can display subscription details in its own language.

Instructions

POST /v1/subscriptionLocalizations (POST /v1/subscriptionLocalizations) Body shape: see OpenAPI components.schemas.SubscriptionLocalizationCreateRequest for the full JSON:API envelope.

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": {
      "body": "<body>"
    },
    "name": "subscription_localizations_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.SubscriptionLocalizationCreateRequest.

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 exist, so the description carries the full burden, yet it discloses almost nothing: no auth requirements, no confirmation of what resource is created or returned, no error behavior. The only behavioral hint is that the body must conform to a named schema, which is a pointer rather than disclosure.

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 but wasteful: it repeats the identical route twice in parentheses and then defers entirely to an external document. Nothing is front-loaded that helps an agent decide or act.

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 create operation with a required nested JSON:API body, no annotations, and no output schema, the description should at least summarize the body envelope or the created resource. Instead it outsources everything to an unnamed OpenAPI file, leaving the agent unable to construct a call from the tool definition alone.

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?

There is a single 'body' parameter and schema description coverage is 100%, so the baseline is 3. The description only repeats the schema's pointer to components.schemas.SubscriptionLocalizationCreateRequest, adding no field-level meaning beyond what the schema already says.

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 restates the HTTP route 'POST /v1/subscriptionLocalizations' rather than describing the operation in plain terms. Creation is only inferred from the 'POST' verb and the '_create_instance' name; it never states 'creates a subscription localization.' With ~400 near-identical sibling endpoints, a REST-path echo does not differentiate this tool.

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, no prerequisites, and no mention of relevant alternatives such as subscription_localizations_v2_create_instance or subscription_group_localizations_create_instance. The agent gets nothing about which localization endpoint to pick.

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