Deletes a Game Center group by ID through the App Store Connect API, enabling removal of obsolete or misconfigured groups from your app's Game Center configuration.
DELETE /v1/gameCenterGroups/{id} (DELETE /v1/gameCenterGroups/{id})
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | the id of the requested resource |
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about irreversibility, required permissions, cascade effects on group-linked achievements or leaderboards, or error behavior. For a destructive DELETE endpoint with zero annotation coverage this is a serious gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely short, but the duplicated endpoint string in parentheses is pure redundancy with no informational value, and the definition is under-specified rather than concise. Nothing is front-loaded because there is nothing substantive to front-load.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A destructive operation with no annotations, no output schema, and no explanatory prose leaves the agent without the information needed to invoke it safely. The definition is not complete for a delete tool in a large API surface.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with a single required 'id' parameter already documented as 'the id of the requested resource'. The path template {id} in the description adds no meaning beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is a raw REST endpoint string, 'DELETE /v1/gameCenterGroups/{id}', duplicated in parentheses. It implies deletion of a Game Center group but the parenthetical repeat of the same text adds nothing, and there is no differentiation from siblings such as game_center_groups_update_instance or game_center_groups_get_instance beyond the HTTP verb.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no prerequisites, no mention of alternatives or what happens after deletion. The agent gets no help deciding between this and the update/get/create group tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.