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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_activity_version_releases_get_instance

Retrieve a specific Game Center activity version release by its ID to manage App Store Connect releases. This endpoint is deprecated.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource
includeNocomma-separated list of relationships to include
fields_gameCenterActivityVersionsNothe fields to include for returned resources of type gameCenterActivityVersions
fields_gameCenterActivityVersionReleasesNothe fields to include for returned resources of type gameCenterActivityVersionReleases

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

C2.4/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. It discloses only deprecation status; it says nothing about authentication requirements, rate limits, or what the response contains. Deprecation is genuinely useful, but for a tool with zero annotation coverage this is a thin disclosure.

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 description is short but under-specified rather than concise, and it wastes its one line duplicating the path in parentheses. The deprecation marker is correctly front-loaded, but the repeated route earns no place.

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 read tool with four parameters, no output schema, and no annotations, the description should at least hint at what is returned or what to use instead of a deprecated endpoint. It supplies neither, leaving the agent with only a raw route string.

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 schema already documents id, include, and both fields_* sparse-fieldset parameters. The description adds no parameter meaning (e.g., accepted values or how 'include' affects the payload), 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 states a verb (GET) and a specific resource path (gameCenterActivityVersionReleases/{id}), so an agent can infer it fetches a single release instance. However, this is essentially the tool name re-expressed as an HTTP route, with no prose clarifying what a 'version release' is or how it differs from the many sibling get_instance tools.

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 only usage signal is the [DEPRECATED] tag, which usefully warns the agent away from the tool but names no replacement or alternative. There is no guidance on when this fetch is appropriate versus the create/delete release siblings or the newer activity-version endpoints.

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