Skip to main content
Glama

jira_create_link

Create a relationship link between two Jira issues by specifying link type, inward issue, and outward issue; check available link types first, then link dependencies such as blocks or is blocked by.

Instructions

Create a relationship link between two Jira issues. Use jira_get_link_types first to see available link types. The inward issue "is affected by" the relationship (e.g., "is blocked by"), and the outward issue "causes" it (e.g., "blocks"). Example: KP-1 blocks KP-2 means inward=KP-2, outward=KP-1, type="Blocks".

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": "jira_create_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional comment explaining why these issues are linked
linkTypeYesLink type name from jira_get_link_types (e.g., "Blocks", "Clones", "Relates")
inwardIssueKeyYesIssue that receives the inward relation (e.g., KP-123 "is blocked by" the outward issue)
outwardIssueKeyYesIssue that has the outward relation (e.g., KP-456 "blocks" the inward 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?

No annotations are supplied, so the description carries the full behavioral burden. It explains mutation directionality well, but says nothing about required permissions, duplicate-link behavior, reversibility, or deletion via jira_delete_link, leaving meaningful gaps for a write operation.

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?

Four tight sentences, front-loaded with the action, then prerequisite, then semantics, then a concrete example. No redundant wording and nothing buried.

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?

Covers purpose, prerequisite, and the confusing directional parameters thoroughly. With no output schema and no annotations, the absence of any statement about the response or failure modes is the remaining gap, but an agent can call the tool correctly from what is given.

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 baseline is 3, but the worked example ('KP-1 blocks KP-2 means inward=KP-2, outward=KP-1') resolves the highest-risk ambiguity in the parameter ordering and adds genuine value beyond the schema's per-field descriptions.

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: 'Create a relationship link between two Jira issues'. The phrase 'between two Jira issues' implicitly separates it from jira_create_remote_link, but no sibling is named, so the differentiation is inferred rather than stated.

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?

Gives an explicit prerequisite ('Use jira_get_link_types first to see available link types') and explains directional semantics for choosing inward vs outward. It does not say when to prefer jira_create_remote_link or what to do if a link already exists.

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