Skip to main content
Glama
0xkillaflow

Redmine MCP Server

by 0xkillaflow

Delete issue relation

redmine_delete_issue_relation
Destructive

Remove a dependency link between issues to correct wrong relations, using the relation ID obtained from listing issue relations.

Instructions

Remove a relation (dependency link) between two issues — the cleanup path for a wrong link, e.g. a false "duplicates" or an inverted "blocks". Takes the RELATION id, not an issue id: call redmine_list_issue_relations with the issue_id first to find the relation and its id. Deleting removes the link in both directions at once (Redmine stores one record and derives the inverse), so there is no second side to clean up. Nothing but the link is touched — both issues, their history, and their other relations are untouched — and the link is restored by a single redmine_create_issue_relation call, so this is far less consequential than deleting an issue. A repeated call fails with a not-found error rather than succeeding quietly.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issue_relation_idYesNumeric id of the RELATION to delete — the `id` field of a relation, NOT an issue id. Get it from `redmine_list_issue_relations` (call it with the issue_id first and pick the relation you mean). Passing an issue id here usually deletes a real but unrelated link rather than failing, so never guess this value.
Behavior5/5

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

Beyond destructiveHint=true, describes bidirectional removal, no side effects on issues, restore method, and repeat-call behavior, all adding context not in annotations.

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?

Slightly long but every sentence is informative; front-loaded with purpose, well-structured.

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 single param, no output schema, and annotations, the description covers purpose, usage, behavioral details, error handling, and recovery completely.

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

Parameters5/5

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

Only one parameter with schema coverage 100%; description warns against passing issue id, explains how to obtain relation id, adding crucial guidance beyond 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?

Clearly states it removes a relation (dependency link) between issues, distinguishes from delete_issue and create_issue_relation, and specifies it takes relation id not issue id.

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 describes when to use (cleanup of wrong links like false duplicates) and provides prerequisite step: call list_issue_relations to find the id.

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