jira-mcp-server

link_issues

Link two Jira issues with a specified relationship type, such as Blocks or Relates, using their issue keys.

Instructions

Link two Jira issues (e.g., Blocks, Relates)

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": {
      "inwardIssueKey": "<inwardIssueKey>",
      "outwardIssueKey": "<outwardIssueKey>",
      "linkType": "<linkType>"
    },
    "name": "link_issues"
  }
}

Input Schema

Name	Required	Description
`linkType`	Yes	The type of link (e.g., 'Blocks', 'Relates')
`inwardIssueKey`	Yes	The key of the issue that is linked from
`outwardIssueKey`	Yes	The key of the issue that is linked to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It does not explain the directional nature of inward/outward links, whether the operation is idempotent, or what happens if the link already exists. The brief description leaves important behavioral assumptions unspecified.

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 a single, concise sentence with no wasted words. It is appropriately short for a simple tool, though it sacrifices depth for brevity.

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

Completeness2/5

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

While the schema covers parameters, the description does not explain the semantics of linking, such as which issue should be inward vs outward, or the expected response. Without annotations or an output schema, the description is insufficient for an agent to understand the full behavior of the operation.

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 description coverage is 100%, with each parameter having a clear description. The main tool description adds only the examples for 'linkType', which duplicate the schema. No additional meaning is provided 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?

The description clearly states the action: 'Link two Jira issues' with examples of link types. This distinguishes it from the sibling 'delete_issue_link' and other issue-related tools.

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?

The intended use is implied by the description and tool name, but there is no explicit guidance on when to use this versus alternatives like delete_issue_link. No prerequisites or exclusions are mentioned.

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