Skip to main content
Glama

game_center_leaderboards_releases_get_to_many_relationship

Fetches the releases linked to a Game Center leaderboard by ID, with an optional page limit. Use it to inspect leaderboard release relationships in App Store Connect.

Instructions

[DEPRECATED] GET /v1/gameCenterLeaderboards/{id}/relationships/releases (GET /v1/gameCenterLeaderboards/{id}/relationships/releases)

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_releases_get_to_many_relationship"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
limitNomaximum resources per page

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?

No annotations are provided, so the description carries the full burden. It discloses only deprecation status; nothing is said about pagination behavior, permissions, whether a release must exist, or what the relationship payload looks like – significant gaps for a relationship-fetch tool.

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 the right ordering. However, the identical path is printed twice inside the parentheses, which is pure redundancy rather than 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 simple two-parameter deprecated relationship GET, deprecation status is the one thing an agent needs, and it is present. Beyond that the definition supplies no information about the relationship semantics, so an agent cannot tell this apart from the many sibling relationship endpoints it manages.

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 both parameters (id, limit), so the schema already documents them fully. The description adds no format, default, or paging syntax detail beyond that, giving the baseline 3.

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 the tool name and a REST path restated twice in parentheses, with no explanation of what a 'releases to-many relationship' actually returns. It does not distinguish this tool from near-identical siblings such as game_center_leaderboards_releases_get_to_many_related or game_center_leaderboard_sets_releases_get_to_many_relationship.

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?

The [DEPRECATED] prefix is a genuine signal to avoid the tool, but no replacement or alternative is named, and there is no guidance on when this relationship endpoint is appropriate versus its _related counterpart.

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