app-publish-mcp

apple_create_version_localization

Add localized metadata to an app version for a specific locale, including description, keywords, and promotional text.

Instructions

Create a new localization for a version

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

Input Schema

Name	Required	Description
`locale`	Yes	Locale code (e.g. ko, en-US, ja)
`keywords`	No	Comma-separated keywords
`whatsNew`	No
`versionId`	Yes	App Store Version ID
`supportUrl`	No
`description`	No
`marketingUrl`	No
`promotionalText`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Mar 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description should disclose behavioral traits like mutation, required permissions, or side effects. It only states 'create' without elaboration on what happens to existing data or error conditions.

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

Conciseness4/5

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

The description is very concise at one sentence, front-loading the key action. While it lacks detail, it avoids redundancy and is easy to scan.

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?

Given the complexity (8 parameters, no output schema, no annotations), the description is insufficient. It does not explain the purpose of localization, expected return values, or how to structure multiple optional fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is low (38%), requiring the description to add meaning. However, it does not explain how parameters like 'description', 'whatsNew', or 'promotionalText' are used together, nor does it clarify the format of 'locale' beyond what the schema provides.

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

Purpose5/5

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

The description clearly states the verb 'Create' and the resource 'localization for a version', distinguishing it from sibling tools like 'apple_update_version_localization' and 'apple_list_version_localizations'.

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?

No guidance is provided on when to use this tool versus alternatives such as updating or listing localizations. The description lacks context on prerequisites (e.g., version must exist) and excludes any when-to-use advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server