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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_leaderboards_get_instance

Retrieves a specific Game Center leaderboard by ID, including optional related details such as localizations and releases.

Instructions

[DEPRECATED] GET /v1/gameCenterLeaderboards/{id} (GET /v1/gameCenterLeaderboards/{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_leaderboards_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
limit_releasesNomaximum number of related releases returned (when they are included)
limit_localizationsNomaximum number of related localizations returned (when they are included)
fields_gameCenterGroupsNothe fields to include for returned resources of type gameCenterGroups
fields_gameCenterDetailsNothe fields to include for returned resources of type gameCenterDetails
fields_gameCenterActivitiesNothe fields to include for returned resources of type gameCenterActivities
fields_gameCenterChallengesNothe fields to include for returned resources of type gameCenterChallenges
fields_gameCenterLeaderboardsNothe fields to include for returned resources of type gameCenterLeaderboards
limit_gameCenterLeaderboardSetsNomaximum number of related gameCenterLeaderboardSets returned (when they are included)
fields_gameCenterLeaderboardSetsNothe fields to include for returned resources of type gameCenterLeaderboardSets
fields_gameCenterLeaderboardReleasesNothe fields to include for returned resources of type gameCenterLeaderboardReleases
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?

With no annotations, the description carries the full behavioral burden but provides almost nothing beyond a deprecation flag. It does not state auth requirements, whether the resource may be absent, or any behavioral differences from the V2 endpoint it is deprecated in favor of.

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 deprecation warning, which is good. But it needlessly duplicates the same path twice in parentheses, adding no information.

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 deprecated read endpoint with a rich 13-parameter schema and no output schema, the description omits the single most useful fact: the replacement tool. An agent invoking this cannot tell what to migrate to or whether relationships/fields behave differently in the V2 variant.

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 13 parameters (include, fields_*, limit_*) are already documented in the schema. The description adds no further meaning about their semantics, so the baseline of 3 applies.

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 conveys the verb (GET) and resource (gameCenterLeaderboards/{id}), so an agent can infer it fetches a single leaderboard. However, it largely restates the tool name in HTTP form rather than describing the operation in task terms, and it does not differentiate from the V2 sibling. The [DEPRECATED] prefix is the only added signal.

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 explicit when-to-use guidance and no named alternative, even though a clear replacement (game_center_leaderboards_v2_get_instance) exists in the sibling list. The [DEPRECATED] tag hints the tool should be avoided, but the description never says what to use instead or under what conditions this endpoint still applies.

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