Skip to main content
Glama
multiinstance-jira-mcp

multiinstance-jira-mcp

by jmeronon-dev

Create issue

jira_create_issue

Create Jira issues with summaries, fields, and light Markdown descriptions, routed to the correct instance by project key mapping or an explicit instance.

Instructions

Create an issue. The description accepts light Markdown (headings, lists, bold, code, links, code fences) and is converted to the format the instance expects. The instance is routed by project key mapping or the 'instance' argument.

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": {
      "summary": "<summary>"
    },
    "name": "jira_create_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelsNo
parentNoParent issue key (sub-tasks, or epics on team-managed projects).
boardIdNoUse the project of this agile board.
dueDateNoYYYY-MM-DD
projectNoProject key. Defaults to the parent's project, the board's project or the instance defaultProject.
summaryYes
assigneeNo'me', email, accountId (Cloud) or username (Data Center).
instanceNoJira 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.
priorityNoPriority name, e.g. 'High'.
issueTypeNoIssue type name (default 'Task'). Use 'Sub-task' with parent.
componentsNoComponent names.
descriptionNo
customFieldsNoExtra raw Jira fields, e.g. {"customfield_10016": 5}. Values are sent as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so safety is covered. The description adds two genuinely useful behavioral facts beyond that: the description field is Markdown-converted server-side, and instance routing follows project-key mapping or the 'instance' argument. It says nothing about required permissions, failure modes, or what happens on invalid custom fields for a 13-parameter mutation tool.

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

Conciseness4/5

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

Three short sentences, front-loaded with the action before the behavioral notes, with no filler. Minor ambiguity in starting a sentence with "The description accepts..." since it reads at first as the tool's description rather than the 'description' parameter.

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?

For a 13-parameter creation tool with no output schema, the description covers the two least obvious behaviors (Markdown conversion and instance routing) but omits what a caller gets back, how defaults like issueType 'Task' resolve, and any error or permission behavior. Adequate but with clear gaps.

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 77%, so the baseline is 3, and the description earns above baseline: it clarifies that 'description' accepts light Markdown with a concrete syntax list (headings, lists, bold, code, links, fences) where the schema has no description for that field, and it restates the instance-routing precedence that governs the 'instance' parameter.

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 opens with a specific verb and resource ("Create an issue"), which is unambiguous against siblings like jira_update_issue or jira_copy_issue. It does not explicitly name a sibling or state the boundary between creating and copying, but the action itself is clear.

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 when-to-use or when-not-to-use guidance, and no mention of alternatives such as jira_copy_issue for duplicating existing issues. The routing sentence explains how an instance is chosen, which is context for calling the tool but not a usage decision between tools.

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