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

App Store Connect MCP Server

by SardorbekR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_version_localization

Create a new localization for an App Store version by adding descriptions, keywords, and other metadata in a specific locale.

Instructions

Create a new localization for an App Store version. Add descriptions, keywords, and other metadata in a specific locale.

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

Input Schema

NameRequiredDescriptionDefault
versionIdYesThe App Store version ID
localeYesLocale code (e.g., 'en-US', 'ja', 'zh-Hans')
descriptionNoApp description (max 4000 characters)
keywordsNoKeywords for search (max 100 characters, comma-separated)
whatsNewNoWhat's new in this version (max 4000 characters)
promotionalTextNoPromotional text (max 170 characters)
marketingUrlNoMarketing URL (HTTPS only)
supportUrlNoSupport URL (HTTPS only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states it's a create operation but lacks details on prerequisites, validation, side effects, or uniqueness constraints.

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 with no wasted words. The action and subject are front-loaded, and every sentence adds value.

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?

Given the absence of an output schema and 8 parameters, the description is adequate but lacks details on return value, overwrite behavior, and relationship to sibling tools.

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 the description adds minimal meaning beyond listing parameter types (descriptions, keywords, metadata). Baseline 3 is appropriate as it does not introduce new semantics.

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 an App Store version', distinguishing it from siblings like update_version_localization and delete_version_localization.

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 implies usage for creating a new localization but does not explicitly state when to use it versus alternatives like update_version_localization, nor does it provide exclusions or prerequisites.

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