Skip to main content
Glama
Sign In
app-store-connect-mcp

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_challenge_localizations_create_instance

Create a Game Center challenge localization in App Store Connect to add localized text for a specific challenge. Use this when configuring challenge metadata for multiple languages.

Instructions

POST /v1/gameCenterChallengeLocalizations (POST /v1/gameCenterChallengeLocalizations) Body shape: see OpenAPI components.schemas.GameCenterChallengeLocalizationCreateRequest for the full JSON:API envelope.

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": {
      "body": "<body>"
    },
    "name": "game_center_challenge_localizations_create_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesJSON body. Shape: components.schemas.GameCenterChallengeLocalizationCreateRequest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

D1.8/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no auth/permission requirements, no note that this is a mutating create with irreversible state, no validation or error behavior. It only points at an external OpenAPI schema reference.

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

Conciseness2/5

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

It is short, but the same POST path is printed twice in immediate succession, so a sentence/segment earns nothing. Structure is a raw route plus a schema pointer rather than a front-loaded statement of purpose.

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?

For a mutation tool with no annotations and no output schema, the description should at minimum say what is created and what it depends on. Instead it defers entirely to an external schema reference, leaving the agent without enough context to invoke it confidently.

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% and there is a single 'body' parameter, so the baseline is 3. The description adds a pointer to components.schemas.GameCenterChallengeLocalizationCreateRequest, which is marginally useful for locating the envelope shape, but gives no field-level meaning itself.

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

Purpose2/5

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

The description only restates the tool name as an HTTP route: 'POST /v1/gameCenterChallengeLocalizations'. It conveys that a challenge localization instance is created, but does so by tautology with the tool name rather than describing the resource or its effect in human terms, and it does nothing to distinguish this from the many sibling create_instance tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, no prerequisites (e.g. the challenge version or parent relationship the localization attaches to), and no mention of any alternative or sibling tool. The agent is left to infer everything from the name.

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