Skip to main content
Glama

create_jira_issue

Create a new issue in a Jira project by specifying project key, issue type, and summary. Optionally add description, priority, assignee, labels, components, or custom fields.

Instructions

Creates a new issue in a Jira project. You must specify the project, issue type, and a summary. Other fields like description, priority, and assignee are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelsNoA list of labels to add to the new issue.
summaryYesA concise summary or title for the issue.
assigneeNoThe Atlassian account ID of the user to whom the issue should be assigned.
priorityNoThe priority level for the issue (e.g., "High", "Medium", "Low"). Must be a valid priority in the project.
issueTypeYesThe name of the issue type (e.g., "Bug", "Task", "Story"). This must be a valid issue type in the specified project.
componentsNoA list of component names to associate with the new issue.
projectKeyYesThe key of the project in which the issue will be created (e.g., "PROJ").
descriptionNoA detailed description of the issue. Optional.
customFieldsNoA JSON object for setting custom fields. The keys are the custom field IDs (e.g., "customfield_10010") and the values are the data to be set. **For example: `{"customfield_10010": "Value for custom field"}`**.
Behavior2/5

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

With no annotations provided, the description carries full burden. It states the tool creates an issue (write operation) but does not disclose any side effects, permissions required, or behavior like duplicate handling. The description is minimal on behavioral context.

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?

The description is two sentences long, front-loads the core purpose, and avoids unnecessary details or repetition.

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?

Given the tool has 9 parameters, no output schema, and nested objects (customFields), the description covers the basics but lacks information on return values, error handling, or behavior for edge cases like duplicate issues or insufficient permissions.

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

Parameters4/5

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

The input schema has 100% coverage, but the description adds value by summarizing required vs optional fields and providing an example format for customFields, which enhances understanding beyond the schema.

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 new Jira issue and specifies the required fields (project, issue type, summary). It distinguishes from sibling tools like search_jira_issues, read_jira_issue, or add_jira_comment.

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 description notes required and optional fields but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites.

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/dunz/mcp-atlassian'

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