app-store-connect-mcp-server

get_app_store_version_localization

Retrieve detailed information about a specific app store version localization using its localization ID.

Instructions

Get detailed information about a specific app store version localization

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": "get_app_store_version_localization"
  }
}

Input Schema

Name	Required	Description	Default
`localizationId`	Yes	The ID of the app store version localization

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Jul 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must carry the burden of behavioral disclosure. It describes a read operation ('get'), which implies no side effects, but does not clarify error handling, permissions, or rate limits. It adds minimal value beyond the tool name.

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?

The description is a single sentence of 11 words, with zero redundancy. It is front-loaded with the action and resource, making it easy to parse quickly.

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

Completeness3/5

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

While the tool is simple (get by ID), the description does not specify what 'detailed information' includes, especially given no output schema. For full completeness, it could mention expected fields or link to documentation. It is adequate for a straightforward retrieval but lacks depth.

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 coverage is 100% (the single parameter has a description). The tool description adds no extra meaning about the parameter beyond what's in the schema. Baseline is 3 as per guidelines.

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 action ('Get') and the resource ('detailed information about a specific app store version localization'). It effectively distinguishes itself from sibling tools like 'list_app_store_version_localizations' (which lists many) and 'update_app_store_version_localization' (which modifies), indicating a retrieval focus.

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. There is no mention of prerequisites, context, or situations where it should be avoided. Sibling tools exist for listing and updating, but the description offers no comparative advice.

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