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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_achievement_releases_delete_instance

Delete a Game Center achievement release by ID to remove it via App Store Connect API.

Instructions

[DEPRECATED] DELETE /v1/gameCenterAchievementReleases/{id} (DELETE /v1/gameCenterAchievementReleases/{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_achievement_releases_delete_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe id of the requested resource

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/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, yet it only restates the raw endpoint. It does not disclose that the operation is destructive/irreversible, what happens to the release record and its associations, or any auth/permission requirement. The DEPRECATED marker is the only behavioral trait conveyed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded with the [DEPRECATED] warning before the operation. The only waste is the redundant parenthetical that repeats the same path, but overall it is appropriately sized for a simple delete.

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

Completeness3/5

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

For a one-parameter delete with no output schema, minimal description is tolerable, and the deprecation notice is the key piece of context. Still, it omits irreversibility and permission requirements that matter for a destructive operation, leaving it only minimally adequate.

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% with a single 'id' parameter documented as 'the id of the requested resource'. The description adds nothing beyond the path template, so the baseline 3 applies since the schema already does the work.

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

Purpose4/5

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

The description pairs the HTTP verb DELETE with the specific resource path /v1/gameCenterAchievementReleases/{id}, which is unique among siblings (e.g., game_center_achievement_releases_create_instance, game_center_achievement_releases_get_instance). An agent can tell it deletes an achievement release. It stops short of a 5 because the parenthetical merely duplicates the same path verbatim, adding no explanatory value.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The [DEPRECATED] tag is a real usage signal telling the agent to avoid this tool, which is more than most siblings offer. However, no alternative replacement, prerequisite, or condition for use is named, so usage is only implied.

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