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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_leaderboard_sets_v2_get_instance

Retrieves a specific Game Center leaderboard set by ID, optionally including related details, groups, leaderboards, and versions via sparse field and relationship parameters.

Instructions

GET /v2/gameCenterLeaderboardSets/{id} (GET /v2/gameCenterLeaderboardSets/{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_sets_v2_get_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
limit_versionsNomaximum number of related versions 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
limit_gameCenterLeaderboardsNomaximum number of related gameCenterLeaderboards returned (when they are included)
fields_gameCenterLeaderboardsNothe fields to include for returned resources of type gameCenterLeaderboards
fields_gameCenterLeaderboardSetsNothe fields to include for returned resources of type gameCenterLeaderboardSets
fields_gameCenterLeaderboardSetVersionsNothe fields to include for returned resources of type gameCenterLeaderboardSetVersions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.1/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 entire behavioral burden, and it discloses only the HTTP verb, which implies a read-only single-resource fetch. It says nothing about authentication requirements, error behavior (e.g. 404 for bad id), or whether sparse fieldsets/relationships are expanded by default.

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?

The text is short but not concise in a useful sense: the parenthetical repeats the exact same path string, which is pure redundancy, and the definition is too under-specified to be actionable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter tool with no annotations and no output schema, the description provides nothing an agent needs to call it correctly. It omits purpose, usage, behavioral traits, and any hint about the shape of the returned leaderboard set, making it wholly inadequate.

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 all nine parameters (id, include, limit_versions, fields_*) are already documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 is essentially a restatement of the name and HTTP path ('GET /v2/gameCenterLeaderboardSets/{id}') with the same string duplicated in parentheses. It tells the agent almost nothing functional about what a game center leaderboard set is or what retrieving one returns, and does not distinguish itself from siblings like game_center_leaderboard_sets_get_instance (v1) or the various relationship endpoints.

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 tool versus the v1 variant or the many game_center_leaderboard_sets_v2_* relationship tools. No prerequisites or context are given, leaving the agent to infer usage entirely from the tool 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