Skip to main content
Glama
Sign In
App Store Connect MCP Server

App Store Connect MCP Server

by yunyang088
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_app_info_localization

Create localized app info in App Store Connect, including app name, subtitle, and privacy URLs or text. Provide a locale plus appId or appInfoId to add translations.

Instructions

Create a new app info localization (localized app name/subtitle). Provide either appInfoId directly, or appId to resolve the current (non-REPLACED) app info automatically.

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": {
      "locale": "<locale>"
    },
    "name": "create_app_info_localization"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLocalized app name (optional)
appIdNoThe ID of the app; the current app info is resolved automatically (optional if appInfoId is provided)
localeYesThe locale for the localization (e.g. 'zh-Hans', 'ja', 'en-US')
subtitleNoLocalized app subtitle (optional)
appInfoIdNoThe ID of the app info (optional if appId is provided)
privacyPolicyUrlNoPrivacy policy URL for this locale (optional)
privacyChoicesUrlNoPrivacy choices URL for this locale (optional)
privacyPolicyTextNoPrivacy policy text for this locale (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.3

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden. It usefully discloses the auto-resolution behavior (appId resolves the current non-REPLACED app info), which is real behavioral context, but omits permissions required, whether duplicate locales error, and what a failed resolve does.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the input-mutual-exclusivity rule is front-loaded right after the purpose. Every clause earns its place.

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

Completeness4/5

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

For an 8-parameter create tool with no annotations and no output schema, the key ambiguity (which identifier to supply) is resolved. Remaining gaps — permissions, duplicate-locale behavior, return value — are minor but real.

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 every parameter already documents itself including the appInfoId/appId alternation. The description restates that alternation rather than adding syntax, constraints, or defaults beyond the schema.

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

Purpose4/5

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

States a specific verb+resource ("Create a new app info localization") and clarifies the payload (localized app name/subtitle). The app-info scope implicitly separates it from sibling create_app_store_version_localization, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a usable branching rule between appInfoId and appId, which is a form of contextual guidance. However, it never states when to choose create over update_app_info_localization, nor any prerequisites/exclusions.

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