Skip to main content
Glama
0xkillaflow

Redmine MCP Server

by 0xkillaflow
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Delete issue

redmine_delete_issue
Destructive

Permanently delete a Redmine issue and all its associated data, including comments, time entries, and attachments. This action cannot be undone.

Instructions

Permanently delete an issue. THIS CANNOT BE UNDONE: Redmine has no trash and no restore, and the delete cascades — the issue's journals (comments), logged time entries, attachments, and relations are destroyed with it, and on many configurations its sub-issues are deleted too. Always confirm with the user before calling, quoting the issue id and subject (use redmine_get_issue to read them back first). In most situations the right tool is redmine_update_issue instead: setting a closed or rejected status_id takes the issue out of the way while keeping its history and staying reversible. Reserve this tool for genuine mistakes — duplicates, spam, or an issue filed in the wrong place. Requires the "Delete issues" permission; without it Redmine answers with a permission error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_idYesNumeric id of the issue to delete permanently. Deletion is irreversible and cascades: the issue's journals (comments), logged time entries, attachments, and relations go with it, and sub-issues may be deleted along with their parent. Confirm the id — and the intent — with the user before calling.

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Description fully details irreversible deletion, cascading effects (journals, time entries, attachments, relations, sub-issues), and permission requirements. This goes beyond annotations (destructiveHint=true) to provide critical context for safe usage.

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

Conciseness5/5

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

Description is concise and well-structured: starts with the core irreversible action, then cascading details, then usage guidelines and alternatives. Every sentence adds value 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?

Given one parameter, no output schema, and presence of annotations, the description is complete. It covers permission requirements, irreversible consequences, and recommends safer alternatives.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter `issue_id` is fully described in the schema, but the description adds actionable guidance: confirm with the user and read the issue back first. This adds value beyond the schema.

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?

Title and description clearly state the tool deletes an issue permanently. It distinguishes itself from the sibling tool `redmine_update_issue`, which is recommended as a safer alternative.

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 (genuine mistakes, duplicates, spam) and when not to (prefer `redmine_update_issue`). Requires user confirmation before calling, with steps to confirm the issue id and subject.

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/0xkillaflow/agama-redmine-mcp'

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