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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_localizations_v2_update_instance

Update an existing subscription localization in App Store Connect by sending a PATCH request with the localization ID and JSON body.

Instructions

PATCH /v2/subscriptionLocalizations/{id} (PATCH /v2/subscriptionLocalizations/{id}) Body shape: see OpenAPI components.schemas.SubscriptionLocalizationV2UpdateRequest 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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "subscription_localizations_v2_update_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
bodyYesJSON body. Shape: components.schemas.SubscriptionLocalizationV2UpdateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.6/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. PATCH implies a partial mutation, but the description does not say what fields can be changed, whether omitted fields are preserved or cleared, what permissions are required, or what the response contains. The only added context is a pointer to the OpenAPI request schema.

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?

It is short, but the route is duplicated verbatim in parentheses, which is pure waste, and the rest defers to an external OpenAPI document rather than conveying information itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation tool with no annotations and no output schema, the description is thin. It relies on the agent having access to components.schemas.SubscriptionLocalizationV2UpdateRequest, which is not part of the provided schema, leaving the actual updatable fields undisclosed.

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% and both parameters (id, body) are documented in the schema. The description merely restates the body schema reference that the schema already contains, adding no meaning about the JSON:API envelope contents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the HTTP route PATCH /v2/subscriptionLocalizations/{id}, from which an agent can infer this updates a v2 subscription localization. However, it never states the operation in plain language and offers no differentiation from the many sibling update tools (e.g. subscription_localizations_update_instance, subscription_group_localizations_v2_update_instance).

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 statement of when to use this tool, prerequisites, or which alternative (the non-v2 subscription_localizations_update_instance) applies. The agent must infer everything from the route string.

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