Skip to main content
Glama
edrich13

MCP Jira Server

by edrich13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jira_create_issue

Create a new Jira issue by specifying project, summary, issue type, and optional details like priority, assignee, labels, and custom fields.

Instructions

Create a new Jira issue in a specified project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesThe project key where the issue will be created
summaryYesBrief summary/title of the issue
descriptionNoDetailed description of the issue
issueTypeYesType of issue (e.g., Bug, Task, Story, Epic)
priorityNoPriority level (e.g., High, Medium, Low)
assigneeNoUsername of the person to assign the issue to
labelsNoArray of labels to add to the issue
componentsNoArray of component names
customFieldsNoMap of additional Jira field IDs/keys (e.g., customfield_10211) to include in the fields payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / customFields
      Added value: +{
+  "additionalProperties": true,
+  "description": "Map of additional Jira field IDs/keys (e.g., customfield_10211) to include in the fields payload",
+  "type": "object"
+}
  2. First observedv1.0.3

TDQS

B3.3/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 carry the burden of behavioral disclosure. It states the mutation (creates an issue) but does not mention prerequisites like valid projectKey or issueType, potential side effects, or what the response contains. This is minimal transparency for a mutating 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, front-loaded sentence with no filler. It communicates the core action and target efficiently, though it sacrifices useful context for brevity.

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?

For a 9-parameter creation tool with no annotations and no output schema, the description is incomplete. It does not mention required parameters, the return value such as issue key or ID, customFields behavior, or any validation expectations. The schema covers parameters, but the description alone is insufficient for correct invocation.

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%, so all parameters are already documented in the schema. The description adds little beyond implicitly tying 'specified project' to projectKey. Baseline 3 applies because the schema handles the parameter documentation burden.

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 uses a specific verb ('Create'), a concrete resource ('new Jira issue'), and a scoping constraint ('in a specified project'). This clearly distinguishes it from sibling tools like jira_update_issue and jira_delete_issue.

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

Usage Guidelines3/5

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

The intended use is implied by the verb 'Create'—use it to create issues rather than update or search them—but no explicit when-to-use, exclusions, or alternative guidance is provided. The description does not help an agent decide between this and related issue tools beyond the core action.

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