Skip to main content
Glama

jira_create_remote_link

Add a remote link from a Jira issue to an external URL such as a web page, documentation, GitHub PR, or Confluence page.

Instructions

Add a link from a Jira issue to an external URL (web page, documentation, GitHub PR, Confluence page, etc.). Unlike issue links, remote links point to resources outside Jira.

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": {
      "issueKey": "<issueKey>",
      "url": "<url>",
      "title": "<title>"
    },
    "name": "jira_create_remote_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to link to (e.g., https://github.com/org/repo/pull/123)
titleYesDisplay title for the link
summaryNoBrief description of the linked resource
issueKeyYesIssue key to add the link to (e.g., KP-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden for a mutation tool. It says a link is added but is silent on idempotency/duplicate handling, required permissions, and what the call returns — all material for an agent deciding to invoke 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?

Two short sentences, zero filler, with the definition of the resource front-loaded and the differentiation immediately after.

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

Completeness3/5

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

With four well-documented parameters and no output schema, the description covers what the tool creates and how it differs from siblings. However, for an unannotated write tool it leaves behavioral questions (duplicates, permissions, response) unanswered.

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%, so every parameter (url, title, summary, issueKey) is already documented with examples. The description adds no additional meaning about parameter behavior, so baseline 3 applies.

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 ('Add a link from a Jira issue to an external URL') and immediately distinguishes itself from sibling jira_create_link by contrasting remote links with issue links. The parenthetical examples of link targets make the scope unambiguous.

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?

The 'Unlike issue links, remote links point to resources outside Jira' clause effectively tells the agent when to pick this over jira_create_link. It lacks explicit exclusions (e.g., what to do if a link already exists) or prerequisites, but the selection context is clear.

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