app-publish-mcp

apple_update_version_localization

Update an Apple App Store version localization's metadata, including description, keywords, what's new, promotional text, marketing URL, and support URL for a given localization ID.

Instructions

Update localization fields (description, keywords, whatsNew, etc)

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": {
      "localizationId": "<localizationId>"
    },
    "name": "apple_update_version_localization"
  }
}

Input Schema

Name	Required	Description
`keywords`	No	Comma-separated keywords
`whatsNew`	No
`supportUrl`	No
`description`	No
`marketingUrl`	No
`localizationId`	Yes	Localization ID
`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?

While the description indicates mutation, it fails to disclose behavioral details such as whether fields are overwritten or merged, constraints on field values (e.g., length limits), or idempotency. With no annotations provided, the description should cover these but does not.

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 a single concise sentence that efficiently conveys the basic purpose. However, it could be more informative without becoming verbose.

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 tool has 7 parameters, no output schema, and no annotations, the description is incomplete. It lacks details about return values, side effects, and required context (e.g., that localizationId must correspond to an existing version localization), leaving the agent underinformed.

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 coverage is low (29%), and the description merely lists field names without adding constraints, formats, or usage context. It does not compensate for the missing schema descriptions, providing little additional meaning beyond the field names.

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 'Update' and the resource 'localization fields', listing example fields. The tool name and description distinguish it from sibling tools like create and list operations.

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 on when to use this tool versus alternatives, no mention of prerequisites (e.g., needing a localization ID from a prior list call), and no exclusions or scenarios where it should not be used.

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

Deploy Server