Skip to main content
Glama
Sign In
Jira Enterprise MCP

Jira Enterprise MCP

by w-10-m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jira_create_issue

Create Jira issues in any project by specifying issue type, summary, and optional description.

Instructions

Create a Jira issue in the given project.

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

Input Schema

NameRequiredDescriptionDefault
summaryYesShort issue summary
issueTypeYesIssue type name, for example Task, Story, or Bug.
projectKeyNoProject key. Falls back to JIRA_DEFAULT_PROJECT if omitted.
descriptionNoIssue description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states 'Create a Jira issue' without disclosing behavioral traits like permissions needed, whether the issue is created immediately, or what the response looks like. This is insufficient for a creation 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 very short and to the point—one sentence with no unnecessary words. It is appropriately front-loaded and gets the key idea across, though it could be slightly more detailed.

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?

Given the lack of annotations and output schema, the description should provide more completeness. It omits return value information, required permissions, and error conditions. For a creation tool with 4 parameters, this is inadequate.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds no additional meaning beyond the schema, e.g., it does not clarify in-depth usage of 'summary' or 'description' fields.

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 clearly states the tool creates a Jira issue in a given project, which is specific and distinct from sibling tools like jira_update_issue or jira_add_comment. The verb 'Create' and resource 'Jira issue' are clearly identified.

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?

No guidance is provided on when to use this tool versus alternatives, such as when to use jira_get_create_meta first or prerequisites like required permissions. The description does not indicate any context or exclusions.

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

Deploy Server

Other Tools