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

app-store-connect-mcp

by devinwang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

app_store_versions_delete_instance

Delete an App Store version by ID to remove it from App Store Connect. Use when you need to permanently remove a specific version record.

Instructions

DELETE /v1/appStoreVersions/{id} (DELETE /v1/appStoreVersions/{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": "app_store_versions_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

D1.7/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, and it supplies nothing beyond the word DELETE. It does not state that the operation is irreversible, that related resources (localizations, screenshot sets, review details) may be affected, what permissions are required, or what a successful/error 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?

It is short, but roughly half the text is a pointless parenthetical duplicate of the first half. Brevity here reflects under-specification rather than disciplined conciseness.

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

Completeness1/5

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

For a destructive DELETE endpoint with no annotations and no output schema, the description omits every operational detail an agent needs: destructiveness, reversibility, side effects on child resources, and error conditions.

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 there is a single required 'id' parameter already documented as 'the id of the requested resource'. The description adds nothing about the parameter, so the baseline 3 applies since the schema does the work.

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 the raw HTTP route 'DELETE /v1/appStoreVersions/{id}', duplicated verbatim in parentheses. It restates the tool name (app_store_versions_delete_instance) rather than explaining the operation, and gives no differentiation from the many sibling delete tools (pass_type_ids_delete_instance, app_preview_sets_delete_instance, etc.).

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

Usage Guidelines1/5

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

No guidance whatsoever on when to delete an app store version versus alternatives, no prerequisites (e.g. version must not be attached to a release or submission), and no named sibling. The agent is left to infer everything from the path string.

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