Skip to main content
Glama
Sign In
Jira MCP

Jira MCP

by ameforge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

unlink_issues

Remove a link between two Jira tickets, regardless of direction. Specify link_type when multiple links connect them to select the right one.

Instructions

Remove a link between two Jira tickets. Direction does not matter. If several links connect them, pass link_type to pick one.

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": {
      "linked_ticket_id": "<linked_ticket_id>",
      "ticket_id": "<ticket_id>"
    },
    "name": "unlink_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
link_typeNoLink type name or verb, e.g. "Blocks", "Relates", "is bug of"
ticket_idYesJira issue key, e.g. GEM-1
linked_ticket_idYesThe other issue key, e.g. GEM-2

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that link direction is irrelevant and that multiple links can coexist, but says nothing about permissions, error behavior for nonexistent links, or whether only the matching link type is removed.

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?

Three short sentences, front-loaded with the core action, then the two behavioral caveats. No filler or redundancy.

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 simple three-parameter tool with full schema coverage and no output schema, the description covers the essential action and the multi-link case. Minor gaps remain around failure modes and permissions, but nothing an agent needs to invoke it is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: link_type is optional and only needed when several links connect the two issues, which the schema's 'Link type name or verb' text does not convey.

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

Purpose4/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 tickets.' The inverse relationship to the sibling link_issues is inferable, but the description never names or contrasts that sibling explicitly, so it falls short of the top score.

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

Usage Guidelines3/5

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

Usage is only implied by the operation itself. It explains the link_type disambiguation case ('If several links connect them, pass link_type to pick one') but gives no guidance on when to use this versus link_issues or what prerequisites exist.

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

Deploy Server

Other Tools