Skip to main content
Glama

create_issue

Create a Jira issue—epic, task, story, or sub-task—with custom fields, parent links, and assignee. Returns key and URL for reuse.

Instructions

Create a Jira issue — epic, task, story or sub-task.

CALL THIS TOOL STRICTLY ON THE USER'S EXPLICIT REQUEST. It writes a real issue into the project under the token owner's name and this server cannot delete it afterwards. Never create issues on your own initiative (not to "track" work you are doing, not as an inferred step of another request). When several issues are described at once, confirm the list with the user before creating them.

Args: project_key: Target project key, e.g. PROJ. summary: Single-line title of the issue. issue_type: Type name as it appears in Jira — Task (default), Epic, Story, Bug, Sub-task… Call get_issue_types when unsure; names are instance-specific and may be localised. description: Body text (plain text / Jira wiki markup). parent: Key of the parent issue. For a sub-task this is its parent task (required). For any other type this is the epic it belongs to — it is written to the Epic Link field. epic_name: Short board label for an epic. Epics only; defaults to summary when omitted. assignee: Username (Server/DC login) to assign the issue to. priority: Priority name, e.g. Major. labels: Labels to set. components: Component names to set. due_date: Due date, YYYY-MM-DD. extra_fields: Raw field overrides merged in last, for anything this signature does not cover — e.g. story points or a required custom field: {"customfield_10004": 3}.

Returns the created issue: key, id, url and the resolved type/parent, so the key can be reused directly (e.g. as parent for the epic's children).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNo
parentNo
summaryYes
assigneeNo
due_dateNo
priorityNo
epic_nameNo
componentsNo
issue_typeNoTask
descriptionNo
project_keyYes
extra_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: it writes a real issue, cannot be deleted, runs under the token owner's name, and returns the created issue's key/id/url. No contradictions with missing annotations.

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 well-structured with headers and bullet points, front-loading the core purpose and usage guidelines. While slightly verbose, every sentence adds value, earning a high score.

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

Completeness5/5

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

Given the tool's complexity (12 parameters, 2 required, output schema present), the description covers all parameters, usage guidelines, and return values comprehensively, leaving no gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries full burden. It explains each parameter in detail with examples, defaults, and relationships (e.g., parent for sub-task vs epic), far exceeding what the schema provides.

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 'Create a Jira issue — epic, task, story or sub-task.' It uses a specific verb and resource, and distinguishes from siblings by listing the supported issue types, making the purpose unmistakable.

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

Usage Guidelines5/5

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

The description explicitly says 'CALL THIS TOOL STRICTLY ON THE USER'S EXPLICIT REQUEST' and warns against creating issues on its own initiative. It also advises confirming a list of issues with the user, providing clear when-not and usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nsleader/jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server