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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_leaderboard_localizations_v2_get_instance

Retrieve a Game Center leaderboard localization by ID from App Store Connect. Fetch locale, name, formatter settings, version, or image relationships for a specific localization.

Instructions

GET /v2/gameCenterLeaderboardLocalizations/{id} (GET /v2/gameCenterLeaderboardLocalizations/{id})

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": {
      "id": "<id>"
    },
    "name": "game_center_leaderboard_localizations_v2_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_gameCenterLeaderboardImagesNothe fields to include for returned resources of type gameCenterLeaderboardImages
fields_gameCenterLeaderboardVersionsNothe fields to include for returned resources of type gameCenterLeaderboardVersions
fields_gameCenterLeaderboardLocalizationsNothe fields to include for returned resources of type gameCenterLeaderboardLocalizations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.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 carries the full behavioral burden, yet it only conveys read-only GET semantics implied by the HTTP verb. It says nothing about authentication requirements, error behavior, pagination, or how sparse fieldsets/includes affect the response.

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?

The description is very short, but it wastes space by duplicating the endpoint path in parentheses and is essentially front-loaded with only a route. It is concise but under-specified rather than efficiently informative.

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 resource with five parameters including sparse fieldsets and relationship includes, and no output schema, the description is insufficient. It does not explain what the call returns, how includes/fields interact, or any constraints an agent would need to invoke it correctly.

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 JSON schema already documents all five parameters, including id, include, and the three fields_* sparse fieldset options. The description adds no parameter meaning beyond the schema, which meets the baseline 3 for high coverage.

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

Purpose3/5

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

The description identifies a GET operation on a specific resource path (gameCenterLeaderboardLocalizations v2) with an ID, so the verb and resource are present. However, it is a raw endpoint string repeated twice in parentheses and gives no differentiation from sibling game_center_leaderboard_localizations_get_instance (v1) or the v2 image relationship tool.

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 statement of when to use this tool versus alternatives such as the v1 get instance, the v2 image relationship, or collection endpoints. The only implied usage is fetching one resource by ID, which a caller must infer from the path.

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