Remove an App Store version by providing its unique ID. Use this endpoint to delete a version that is no longer needed, cleaning up your app's version list.
Delete an App Store version. [DELETE /v1/appStoreVersions/{id}]
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID from the matching list call. |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / id / descriptionAdded value: +"ID from the matching list call."v2.0.0Input schema / properties / id / descriptionRemoved value: -"Resource identifier."v1.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is destructive. The description adds no extra context beyond the endpoint; it does not mention irreversibility, cascading effects, or consequences beyond what annotations convey.
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?
The description is a single sentence plus endpoint, with no unnecessary words. It is perfectly concise and front-loaded.
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?
For a simple delete tool with one parameter, no output schema, and strong annotations covering destructive/idempotent hints, the description is largely complete. It could mention any state restrictions (e.g., versions only deletable in certain states), but this is not essential for basic functionality.
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 description coverage is 100%, with the id parameter described as 'ID from the matching list call.' This is clear and sufficient; the description adds no additional meaning beyond the schema.
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 clearly states 'Delete an App Store version' with a specific verb and resource, and includes the API endpoint. This unambiguously distinguishes it from sibling tools like create, update, and get.
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 guidance is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The context is only implied by the tool name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.