Skip to main content
Glama

jira_get_remote_links

Retrieves all external URL links attached to a Jira issue by issue key, such as GitHub PRs, docs, and related websites. Use it to audit resources outside Jira, not Jira-to-Jira issue links.

Instructions

Get all external URL links attached to a Jira issue. These are links to resources outside Jira like GitHub PRs, documentation pages, or related websites. Different from issue links which connect Jira issues to each other.

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>"
    },
    "name": "jira_get_remote_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueKeyYesIssue key to get external links for (e.g., KP-123)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the result set is external-URL links and that all of them are returned ("Get all"), but says nothing about permission requirements, pagination, behavior when no links exist, or response shape.

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 and followed by scope clarification and differentiation. Every sentence carries information and none is redundant.

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 single-parameter read tool with no output schema and no annotations, the description covers what is fetched and how it differs from related concepts. The remaining gap is the absence of any note on what happens with a key that has no remote links or how results are returned.

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?

There is a single parameter with 100% schema description coverage, including an example format (KP-123), so the schema already does the work. The description adds no extra meaning about the issueKey beyond what the schema states, which matches the baseline 3 for fully covered schemas.

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 uses a specific verb plus resource ("Get all external URL links attached to a Jira issue") and immediately clarifies the concept boundary against issue links, which connect Jira issues to each other. An agent can distinguish it from jira_get_issue or jira_create_link without opening the schema.

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?

It establishes clear usage context by defining the resource as external URLs such as GitHub PRs, docs, or related sites, and explicitly rules out the similarly named issue-links concept. It does not name sibling tools such as jira_get_link_types or jira_create_remote_link as alternatives, so the routing guidance is clear but not exhaustive.

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