Skip to main content
Glama
akhilthomas236

MCP Jira & Confluence Server

create-jira-issue

Create a new Jira issue by specifying project key, summary, and issue type, with optional description and assignee.

Instructions

Create a new Jira issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_keyYes
summaryYes
issue_typeYes
descriptionNo
assigneeNo

Implementation Reference

  • The tool 'create-jira-issue' is registered in the handle_list_tools() function with its name, description, and JSON Schema input schema. Required arguments: project_key, summary, issue_type. Optional arguments: description, assignee.
    return [
        types.Tool(
            name="create-jira-issue",
            description="Create a new Jira issue",
            inputSchema={
                "type": "object",
                "properties": {
                    "project_key": {"type": "string"},
                    "summary": {"type": "string"},
                    "issue_type": {"type": "string"},
                    "description": {"type": "string"},
                    "assignee": {"type": "string"},
                },
                "required": ["project_key", "summary", "issue_type"],
            },
        ),
  • The handler for 'create-jira-issue' in handle_call_tool(). It extracts arguments (project_key, summary, issue_type, description, assignee), calls jira_client.create_issue(), and returns a TextContent + EmbeddedResource response with the created issue key.
    if name == "create-jira-issue":
        project_key = arguments.get("project_key")
        summary = arguments.get("summary")
        issue_type = arguments.get("issue_type")
        description = arguments.get("description")
        assignee = arguments.get("assignee")
        
        if not project_key or not summary or not issue_type:
            raise ValueError("Missing required arguments: project_key, summary, and issue_type")
            
        result = await jira_client.create_issue(
            project_key=project_key,
            summary=summary,
            issue_type=issue_type,
            description=description,
            assignee=assignee
        )
        
        issue_key = result.get("key")
        if not issue_key:
            raise ValueError("Failed to create Jira issue, no issue key returned")
            
        return [
            types.TextContent(
                type="text",
                text=f"Created Jira issue {issue_key}",
            ),
            types.EmbeddedResource(
                type="resource",
                resource=types.TextResourceContents(
                    uri=AnyUrl(build_jira_uri(issue_key)),
                    text=f"Created Jira issue: {issue_key}",
                    mimeType="text/markdown"
                )
            )
        ]
  • The jira_client.create_issue() method in JiraClient. It constructs the Jira API payload with project, summary, issue type, optional description, and optional assignee fields, then POSTs to the Jira API 'issue' endpoint.
    async def create_issue(self, project_key: str, summary: str, issue_type: str, 
                          description: Optional[str] = None, 
                          assignee: Optional[str] = None) -> Dict[str, Any]:
        """Create a new issue."""
        data = {
            "fields": {
                "project": {"key": project_key},
                "summary": summary,
                "issuetype": {"name": issue_type},
            }
        }
        
        if description:
            data["fields"]["description"] = description
            
        if assignee:
            data["fields"]["assignee"] = {"name": assignee}
            
        return await self.post("issue", data)
Behavior1/5

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

No annotations exist, so description is the sole source. It does not disclose behavioral traits like permission requirements, side effects, or response shape. The brevity provides no transparency beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, but it is under-specified rather than concise. It fails to convey necessary details, so it does not earn its place as a complete description.

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

Completeness1/5

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

Given 5 parameters, no output schema, and no annotations, the description is severely incomplete. It leaves critical gaps about parameter meanings, return values, and usage context.

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

Parameters1/5

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

Schema description coverage is 0%, meaning no parameter descriptions in schema. The description does not add any meaning to parameters like project_key, summary, or issue_type, leaving the agent guessing their purpose.

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?

Description 'Create a new Jira issue' clearly states verb and resource, avoiding tautology. However, it lacks specificity about the type of issue or project context, and does not distinguish from sibling tools like comment-jira-issue or transition-jira-issue.

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?

No guidance provided on when to use this tool versus alternatives. No mention of prerequisites, required fields, or situations where another tool would be more appropriate.

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

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