Add a locale to an editable custom product page version in App Store Connect, defining the version ID, locale code, and optional promotional text for localized store listings.
Add a locale to an editable custom product page version
| Name | Required | Description | Default |
|---|---|---|---|
| locale | Yes | Locale code, e.g. en-US | |
| versionId | Yes | ||
| promotionalText | No |
Changes observed during successful MCP inspections.
v0.7.0Does 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 mentions the 'editable' precondition, which is useful, but it does not explain mutation effects, permissions, error cases, or what happens to existing localizations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is a single front-loaded sentence with no wasted wording. It is appropriately concise for the core operation, even though it is sparse overall.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations, no output schema, and incomplete parameter documentation, the description is too thin. It does not give enough context about return behavior, required version state beyond 'editable', or how this differs from updating an existing localization.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 33%: locale is documented in the schema, but versionId and promotionalText are not. The description adds some meaning to versionId by implying it must identify an editable version, but it says nothing about promotionalText and does not compensate for the low schema coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('Add') and resource ('locale to an editable custom product page version'), making the operation clear. It does not explicitly contrast with sibling tools such as update_custom_product_page_localization or delete_custom_product_page_localization, so sibling differentiation is left implicit.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by 'editable custom product page version' and the create-style verb, but there is no explicit when-to-use guidance or comparison to update/delete/list localization tools. An agent can infer the basic scenario but is not told prerequisites or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.