jira-mcp-server

create_issue

Create a new Jira issue by specifying project key, summary, issue type, priority, and description.

Instructions

Create a new Jira issue

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

Input Schema

Name	Required	Description	Default
`summary`	Yes	Short summary of the issue
`priority`	No	Priority (e.g., High, Medium, Low)
`issueType`	No	Type of issue (e.g., Task, Bug, Story)	Task
`projectKey`	Yes	Project key (e.g., PROJ)
`description`	No	Detailed description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says a new issue is created, with no mention of required permissions, default fields, notifications, or potential side effects. This is insufficient for a 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?

The description is a single concise sentence that is appropriately sized for a simple tool. It is front-loaded with the action and resource, though it lacks any additional useful context.

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

Completeness2/5

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

With no annotations and no output schema, the description is the only source of behavioral context. It does not explain the return value, error cases, or how it differs from bulk creation. Given the complexity of creating a Jira issue, this is incomplete.

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%, with each parameter having a clear description. The tool description adds nothing beyond the schema, but baseline 3 applies because the schema already documents parameters well.

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 uses a specific verb ('Create') and resource ('a new Jira issue'), clearly indicating the tool's function. It is distinguishable from obvious siblings like search_issues or update_issue, but does not explicitly differentiate from create_subtask or bulk_create_issues.

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?

The description provides no guidance on when to use this tool versus alternatives such as bulk_create_issues or create_subtask. It implies single-issue creation but does not state exclusions or preferred use cases.

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