Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Copy issue between instances

jira_copy_issue

Copy a Jira issue to another instance or project, including summary, description, and labels, with optional priority, comments, and cross-reference links.

Instructions

Copy an issue (summary, description, labels, optionally priority and comments) from one Jira instance to a project on another instance — or the same one. Adds cross-reference comments when linkBack is true.

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": {
      "issue": "<issue>",
      "targetInstance": "<targetInstance>",
      "targetProject": "<targetProject>"
    },
    "name": "jira_copy_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueYesIssue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123').
linkBackNoAdd a note with the counterpart URL on both issues (default true).
issueTypeNoIssue type on the target (default: same name as the source).
copyCommentsNoAlso copy comments as text (default false).
copyPriorityNoCopy priority by name (default false; names often differ).
targetProjectYesProject key on the target instance.
sourceInstanceNoJira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists.
targetInstanceYesInstance that receives the copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say non-read-only, non-destructive, open-world; the description adds real context beyond that by disclosing that linkBack writes counterpart comments on BOTH the source and target issues, so the source is mutated too. It does not cover failure modes for an unreachable target instance, authentication across instances, or what is deliberately not copied (attachments, subtasks).

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 tight sentences, front-loaded with verb, resource and copied-field scope, then the linkBack side effect. No filler or repeated information.

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 an 8-parameter, open-world, cross-instance mutation with no output schema, the description covers what is copied, what is optional, routing defaults and the linkBack side effect. The main omission is what the call returns (presumably the new issue key/URL) and whether the target project or issue type must pre-exist.

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%, so every parameter already carries its own default and explanation (linkBack default true, copyComments/copyPriority default false, sourceInstance routing rules). The description mostly restates the same field list and adds no syntax or format detail beyond the schema; 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 (copy an issue) and enumerates exactly which fields travel (summary, description, labels, optionally priority and comments), plus the source/target scope. It is clearly distinguishable from jira_create_issue and jira_update_issue without opening any 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?

Establishes the scenario clearly — cross-instance migration, explicitly allowing the degenerate same-instance case — which is the main context an agent needs to select it. It stops short of naming alternatives or stating when not to use it (e.g. when a plain jira_create_issue on the local instance would suffice).

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