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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_achievement_localizations_v2_delete_instance

Delete a Game Center achievement localization by ID to remove an outdated locale entry from App Store Connect.

Instructions

DELETE /v2/gameCenterAchievementLocalizations/{id} (DELETE /v2/gameCenterAchievementLocalizations/{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_localizations_v2_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

C2.2/5.0
Behavior1/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 of behavioral disclosure, and it discloses nothing: no statement that the deletion is irreversible, what happens to dependent resources, whether the id must exist, or what an error looks like. The word DELETE merely repeats the tool name.

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 wasteful: the same path is written twice, once as raw HTTP syntax and once in parentheses, adding no information. Nothing is front-loaded about what is being deleted or the consequences.

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 destructive single-parameter delete with no annotations and no output schema, the description should at minimum state irreversibility and any preconditions. The schema is complete, but the behavioral context an agent needs before invoking a delete is entirely absent.

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 the single required id parameter, so the schema already documents the argument fully. The description adds no format, scope, or constraint detail beyond the endpoint template. Baseline 3 applies when the schema does the heavy lifting.

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 gives a concrete verb and resource (DELETE on gameCenterAchievementLocalizations by id), so the operation is identifiable. However, it is essentially a restatement of the tool name and endpoint, with no explanation of what a 'localization' is or how this differs from the v1 delete sibling (game_center_achievement_localizations_delete_instance) or the v2 update/get variants.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as the v1 delete tool or the update tool. The only hint is the HTTP verb itself, which the agent must infer from the name anyway.

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