Skip to main content
Glama

Delete version

delete_version
Destructive

Permanently delete a version created by mistake; close the version instead for finished releases or sprints. Work packages are not deleted but lose the version.

Instructions

Permanently delete a version.

Use it only for a version created by mistake. For a finished release or sprint, update_version(status='closed') is almost always the right answer: it keeps the history and stops new assignments.

Returns a small confirmation once OpenProject accepts the deletion. Work packages are NOT deleted — they simply lose their version — but that only happens on instances that allow the deletion at all.

Pitfalls: OpenProject refuses (422) to delete a version that work packages still reference; the error hint explains how to find them. Deleting a shared version affects every project that used it. The 'manage versions' permission is required, so a 403 is about the account.

Cross-references: list_versions for the id; update_version(status='closed') for the reversible alternative; list_work_packages to find what still points at the version before removing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoMust be true. Ask the user first: there is no undo. Calling with confirm=false returns a confirmation_required error and deletes nothing.
version_idYesNumeric version id to delete. Read it back with list_versions first — version names repeat across projects, ids do not.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the version that was deleted.
deletedYesTrue once OpenProject accepted the deletion.
messageYesHuman-readable confirmation.
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses key behaviors beyond annotations: work packages are NOT deleted, 422 refusal on referenced versions, 403 permission requirement, and shared version impact. This goes well beyond the destructiveHint annotation and adds context that affects the agent's decision-making.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured with separate paragraphs for usage guidance, side effects, and pitfalls. Each sentence carries useful information, though a few could be merged. It earns a 4 for density without redundancy.

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

Completeness5/5

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

Covers prerequisites (list_versions), alternatives (update_version), side effects (shared versions, work packages), error scenarios (422, 403), and confirmation flow. With an output schema present, no need to describe return values. Complete for a destructive mutation.

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 coverage is 100% with detailed descriptions for both params (confirm must be true, version_id numeric and from list_versions). The description reinforces these points (e.g., 'Ask the user first') but adds little beyond schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Permanently delete a version' with a specific verb and resource, clearly distinguishing it from the reversible alternative update_version(status='closed'). It also clarifies the scope (work packages are not deleted, only lose their version).

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

Usage Guidelines5/5

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

Explicitly states when to use ('only for a version created by mistake') and when not to (for a finished release or sprint, use update_version(status='closed')). Cross-references list_versions and list_work_packages for prerequisites and pre-removal checks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kar-thik/openproject-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server