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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

subscription_group_localizations_v2_update_instance

Update localized metadata, such as display name and description, for an App Store subscription group by sending a PATCH request to its localization ID.

Instructions

PATCH /v2/subscriptionGroupLocalizations/{id} (PATCH /v2/subscriptionGroupLocalizations/{id}) Body shape: see OpenAPI components.schemas.SubscriptionGroupLocalizationV2UpdateRequest 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_group_localizations_v2_update_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.1/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, yet it discloses nothing: not whether PATCH merges or replaces unspecified fields, not required permissions or auth scope, not whether the change is reversible, not what the response contains. Pointing at an external OpenAPI component name is not usable disclosure for an agent that has no access to that document at call time.

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 parenthetical duplicate of the same path is pure waste, and the single remaining sentence is a pointer to external documentation rather than an explanation. Front-loading is fine but the content is hollow.

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 mutation tool with zero annotations, no output schema, and a nested JSON:API body whose shape is only referenced by name, the description should at minimum explain the update semantics and the envelope requirement. It defers everything to an OpenAPI document that is not part of the tool definition.

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' is documented as the resource id and 'body' is documented as a JSON:API envelope pointing at the same schema component. The description adds nothing beyond repeating the body pointer, so the baseline 3 for fully covered schemas applies.

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 tool name as a URL: 'PATCH /v2/subscriptionGroupLocalizations/{id}', duplicated verbatim in parentheses. It conveys only that this is a PATCH on a subscription group localization v2 resource, with no plain-language statement of what is being updated (display name, locale, description, etc.). It is essentially a tautology of the identifier rather than a purpose statement.

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 guidance on when to use this tool, no prerequisite (e.g. the localization must already exist), and no mention of the v1 sibling subscription_group_localizations_update_instance or when the v2 variant is preferred. The only implied usage is that an existing resource is being modified, which the agent must infer from 'PATCH'.

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