Skip to main content
Glama

Create Jira issue

create_issue

Create a Jira issue with a project key and summary, plus optional type, priority, labels, assignee, and description. Returns the new issue key and URL for tracking.

Instructions

Create a Jira issue. Returns issue key and URL.

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

Input Schema

NameRequiredDescriptionDefault
labelsNoLabels to set on the issue.
summaryYesIssue title, at most 255 characters.
priorityNoPriority name, e.g. High.
config_idNoJira instance to use, from list_configs. Omit for the default.
issue_typeNoIssue type name, e.g. Task, Bug, Story.Task
descriptionNoPlain-text description. Blank lines separate paragraphs.
project_keyYesProject key, e.g. ONE.
assignee_account_idNoAtlassian account ID of the assignee.

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 readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false, so the safety and mutation profile is covered. The description adds one genuinely useful piece of information beyond that: the return payload (issue key and URL), which compensates for the absent output schema. It says nothing about auth requirements, duplicate creation on retry, or validation failures, so it remains a modest contribution.

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 sentences, zero filler, with the action front-loaded and the return value second. Nothing could be removed without losing information.

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?

With eight parameters, 100% schema coverage, and full annotations, most of the burden is already carried by structured fields, and the description correctly adds the return shape. However, for a write tool that creates records, the absence of any note on required permissions, project existence, or duplicate-creation risk leaves a real gap.

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% and every parameter, including defaults for issue_type and the config_id/list_configs pointer, is documented inline. The description adds no parameter-level meaning at all, so the baseline 3 applies.

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?

States a specific verb and resource ('Create a Jira issue') that an agent can immediately distinguish from siblings like update_issue or transition_issue. It does not explicitly name or contrast with any sibling, which keeps it just short of a 5.

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, no mention of prerequisites such as needing an existing project_key or selecting a Jira instance via list_configs, and no contrast with update_issue. The agent must infer all of this from the schema and sibling names.

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