Jira Cloud MCP Server

create_or_update_remote_issue_link

Create a new remote issue link or update an existing one in Jira Cloud by providing the issue ID or key and the request body with link details.

Instructions

Create or update remote issue link

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": {
      "issueIdOrKey": "<issueIdOrKey>",
      "body": "<body>"
    },
    "name": "create_or_update_remote_issue_link"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes	Request body (JSON object)
`issueIdOrKey`	Yes	The ID or key of the issue.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 30, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It only repeats the create/update semantics already present in the tool name, without explaining what updating entails, whether existing links are overwritten, what happens on conflict, or what permissions/effects are involved.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short but this is under-specification rather than effective conciseness. It provides no added value beyond the tool name and does not earn its place as a helpful explanation for an upsert operation with a nested object.

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

Completeness1/5

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

This is an upsert tool with no output schema, no annotations, and a complex nested body parameter. The description leaves the agent without enough context to construct a correct request body, understand update semantics, or know how the response will look or whether the operation is idempotent.

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 coverage is 100% for the top-level parameters, so baseline is 3. The description adds no parameter meaning beyond the schema. The nested 'body' object contains fields like globalId and relationship that remain unexplained in both the description and the schema.

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?

The description clearly states the verb and resource: 'Create or update remote issue link.' It is unambiguous about the operation, and the 'remote' qualifier distinguishes it from ordinary issue-link tools like link_issues. It lacks richer detail but is not confusing.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as link_issues or get_remote_issue_links. The description implies usage from the verb 'create or update,' but it does not state prerequisites, conditions, or cases where a different tool should be preferred.

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

Deploy Server