Skip to main content
Glama
katsuhirohonda

Jira & Confluence MCP Server

by katsuhirohonda
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

jira_create_issue

Create new Jira issues by specifying project key, summary, description, type, priority, and assignee to track tasks, bugs, or stories.

Instructions

Create a new Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYesProject key
summaryYesIssue summary
descriptionNoIssue description
issue_typeNoIssue type (e.g., Bug, Task, Story)Task
priorityNoPriority (e.g., High, Medium, Low)Medium
assigneeNoAssignee username

Implementation Reference

  • src/jira_server.py:287-309 (handler)
    The main handler function that executes the logic to create a new Jira issue using the atlassian Jira client.
    async def _create_issue(self, arguments: dict) -> List[TextContent]:
    """Create a new Jira issue"""
    fields = {
        "project": {"key": arguments["project_key"]},
        "summary": arguments["summary"],
        "issuetype": {"name": arguments.get("issue_type", "Task")}
    }
    
    if "description" in arguments:
        fields["description"] = arguments["description"]
    
    if "priority" in arguments:
        fields["priority"] = {"name": arguments["priority"]}
    
    if "assignee" in arguments:
        fields["assignee"] = {"name": arguments["assignee"]}
    
    result = self.jira_client.create_issue(fields=fields)
    
    return [TextContent(
        type="text",
        text=f"Created issue: {result['key']}\nURL: {result['self']}"
    )]
  • src/jira_server.py:88-119 (schema)
    The input schema defining the parameters accepted by the jira_create_issue tool, including required project_key and summary.
    inputSchema={
    "type": "object",
    "properties": {
        "project_key": {
            "type": "string",
            "description": "Project key"
        },
        "summary": {
            "type": "string",
            "description": "Issue summary"
        },
        "description": {
            "type": "string",
            "description": "Issue description"
        },
        "issue_type": {
            "type": "string",
            "description": "Issue type (e.g., Bug, Task, Story)",
            "default": "Task"
        },
        "priority": {
            "type": "string",
            "description": "Priority (e.g., High, Medium, Low)",
            "default": "Medium"
        },
        "assignee": {
            "type": "string",
            "description": "Assignee username"
        }
    },
    "required": ["project_key", "summary"]
}
  • src/jira_server.py:85-120 (registration)
    The tool registration in the list_tools() method, defining name, description, and schema.
    Tool(
    name="jira_create_issue",
    description="Create a new Jira issue",
    inputSchema={
        "type": "object",
        "properties": {
            "project_key": {
                "type": "string",
                "description": "Project key"
            },
            "summary": {
                "type": "string",
                "description": "Issue summary"
            },
            "description": {
                "type": "string",
                "description": "Issue description"
            },
            "issue_type": {
                "type": "string",
                "description": "Issue type (e.g., Bug, Task, Story)",
                "default": "Task"
            },
            "priority": {
                "type": "string",
                "description": "Priority (e.g., High, Medium, Low)",
                "default": "Medium"
            },
            "assignee": {
                "type": "string",
                "description": "Assignee username"
            }
        },
        "required": ["project_key", "summary"]
    }
),

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Create a new Jira issue,' implying a write operation, but fails to mention critical aspects such as required permissions, whether the creation is idempotent, error handling, or what happens upon success (e.g., returns an issue ID). This is a significant gap for a mutation tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or redundancy. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly. Every word earns its place, adhering to best practices for conciseness.

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 complexity of creating an issue (a mutation operation) with no annotations and no output schema, the description is incomplete. It doesn't address behavioral traits like authentication needs, error cases, or what the tool returns (e.g., issue key or ID). For a tool with 6 parameters and significant implications, more context is needed to guide the agent effectively.

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%, with all parameters well-documented in the input schema (e.g., project_key, summary, description). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. According to the rules, with high schema coverage (>80%), the baseline is 3 even without param info in the description.

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?

The description clearly states the action ('Create') and resource ('new Jira issue'), making the purpose immediately understandable. It distinguishes from siblings like jira_get_issue or jira_update_issue by specifying creation rather than retrieval or modification. However, it doesn't explicitly differentiate from jira_add_comment or jira_transition_issue in terms of creating vs. adding or transitioning, keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid project key), exclusions, or comparisons to siblings like jira_update_issue for modifying existing issues. This lack of context leaves the agent to infer usage based on tool names alone.

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/katsuhirohonda/jira-confluence-mcp'

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