Skip to main content
Glama

jira_delete_link

Removes a link between two Jira issues by link ID, leaving both issues intact. Get the link ID from the issueLinks array returned by jira_get_issue.

Instructions

Remove a link between two Jira issues. The link ID can be found in the issue details from jira_get_issue (in the issueLinks array). This only removes the relationship, not the issues themselves.

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": {
      "linkId": "<linkId>"
    },
    "name": "jira_delete_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkIdYesLink ID to delete (found in issueLinks when calling jira_get_issue)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the key trait: the deletion is scoped to the relationship and does not destroy the issues. It does not state irreversibility, required permissions, or what happens if the link ID is invalid or already gone, which matter for a destructive operation.

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?

Three short sentences, front-loaded with the action and followed by the practical sourcing hint and the scope caveat. The middle sentence largely duplicates the schema description of linkId, a minor redundancy, but nothing else is wasted.

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

Completeness4/5

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

For a one-parameter, no-output-schema tool this covers purpose, input provenance, and destructiveness scope, which is enough to call it correctly. Only permission requirements and failure behavior are unaddressed, and those are modest gaps at this complexity.

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% for the single linkId parameter, so the baseline is 3. The description's note about finding the ID in issueLinks largely restates the parameter's schema description rather than adding new semantics such as format or valid-ID constraints.

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?

States a specific verb and resource: 'Remove a link between two Jira issues,' and immediately bounds the scope with 'This only removes the relationship, not the issues themselves,' which separates it from jira_delete_issue. An agent can identify the operation and its blast radius without consulting any other field.

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

Usage Guidelines4/5

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

Provides the practical prerequisite context: the link ID comes from jira_get_issue's issueLinks array, which tells the agent where to get its input before calling. It does not explicitly name jira_create_link as the inverse or state when not to use this tool, so it stops short of full routing guidance.

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