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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_center_matchmaking_rule_sets_delete_instance

Delete a Game Center matchmaking rule set by ID in App Store Connect to remove outdated rules and keep matchmaking configurations accurate.

Instructions

DELETE /v1/gameCenterMatchmakingRuleSets/{id} (DELETE /v1/gameCenterMatchmakingRuleSets/{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_matchmaking_rule_sets_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/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 behavioral burden, yet it discloses nothing beyond the verb. It does not state that the operation is irreversible, what dependent resources (rules, teams, queues referencing the set) are affected, what authorization is required, or what a successful response looks like.

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 entirely redundant, repeating the method and path twice in parentheses with zero informational payload. This is under-specification rather than effective conciseness, and nothing is genuinely front-loaded because there is nothing useful to front-load.

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?

With one fully documented parameter and no output schema, the invocation mechanics are inferable, but for a destructive DELETE endpoint with zero annotation coverage the description should at minimum flag irreversibility or side effects. An agent lacks the context to call this safely.

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% and the single required 'id' parameter is documented in the schema as 'the id of the requested resource'. The description adds no syntax, format, or constraint information beyond that, so the baseline of 3 applies.

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 only the HTTP verb plus path, 'DELETE /v1/gameCenterMatchmakingRuleSets/{id}', which is a verbatim restatement of the tool name. It technically names a verb and resource but adds nothing an agent couldn't read from the name, making it a tautology rather than a purpose statement.

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 guidance on when to use this tool, no prerequisites, and no reference to alternative deletion endpoints among the many sibling tools (e.g. game_center_matchmaking_rules_delete_instance or game_center_matchmaking_rule_sets_get_instance). The agent must infer all usage context from the name alone.

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