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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_leaderboard_set_member_localizations_create_instance

Create localized metadata for a Game Center leaderboard set member, enabling localized names and descriptions in App Store Connect.

Instructions

POST /v1/gameCenterLeaderboardSetMemberLocalizations (POST /v1/gameCenterLeaderboardSetMemberLocalizations) Body shape: see OpenAPI components.schemas.GameCenterLeaderboardSetMemberLocalizationCreateRequest 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_leaderboard_set_member_localizations_create_instance"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it discloses almost nothing: no auth requirements, no side effects, no idempotency, no note about the JSON:API envelope constraints beyond a pointer to an external schema. The only added value is naming the request schema, which is not behavioral context.

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

Conciseness3/5

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

It is short and front-loads the endpoint, but the first sentence redundantly repeats the path twice, and the second sentence defers entirely to external OpenAPI docs. Some economy, but the content does not earn much beyond the endpoint identifier.

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?

This is a create mutation with no annotations and no output schema, so the description should convey what gets created and the shape/constraints of the request. Instead it offloads everything to an OpenAPI schema reference, leaving the agent without actionable context for correct invocation.

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% for the single 'body' parameter, so the baseline is 3. The description reinforces that the body follows the GameCenterLeaderboardSetMemberLocalizationCreateRequest envelope, but adds no field-level meaning beyond what the schema already documents.

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 restates the HTTP method and endpoint path ('POST /v1/gameCenterLeaderboardSetMemberLocalizations'), which is essentially a machine-readable echo of the tool name rather than a domain-level statement of what is created. It never explains in human terms that it creates a localization for a Game Center leaderboard set member, and it distinguishes nothing from siblings like update_instance, delete_instance, or get_collection.

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?

There is no guidance on when to use this create endpoint versus its update/delete/get siblings in the same resource family. The agent must infer from the name alone that this is the creation path and cannot tell what prerequisites or context make it appropriate.

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