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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

in_app_purchase_localizations_v2_create_instance

Create a new in-app purchase localization via App Store Connect by sending a JSON:API request body for localized IAP metadata.

Instructions

POST /v2/inAppPurchaseLocalizations (POST /v2/inAppPurchaseLocalizations) Body shape: see OpenAPI components.schemas.InAppPurchaseLocalizationV2CreateRequest 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": "in_app_purchase_localizations_v2_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/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 of behavioral disclosure. It only signals a write via 'POST' and points at a request schema; it says nothing about authentication requirements, side effects, whether the localization is attached to a parent IAP, or what a duplicate-locale conflict would do.

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?

A single front-loaded sentence, but the endpoint is written twice ('POST /v2/inAppPurchaseLocalizations (POST /v2/inAppPurchaseLocalizations)'), which is pure redundancy rather than informative structure.

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 a nested JSON:API body, no annotations, and no output schema, the description is far too thin. It omits required headers/JSON:API envelope details beyond a schema name reference, and gives no sense of the response or failure modes.

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%, so the schema already names the single body parameter and even references components.schemas.InAppPurchaseLocalizationV2CreateRequest. The description merely repeats that pointer, adding no field-level meaning beyond what the schema states; baseline 3 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 does little more than restate the name: 'create' becomes 'POST' and the resource becomes the '/v2/inAppPurchaseLocalizations' path. It never explains what an In-App Purchase localization is or what creating one accomplishes, making it effectively a tautology of the tool name rather than a statement of purpose.

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 versus the v1 sibling (in_app_purchase_localizations_create_instance) or the get/update/delete v2 siblings. No prerequisites, no context about needing an existing IAP to attach the localization to.

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