Skip to main content
Glama
hackdonalds

JIRA MCP Server

by hackdonalds

Create JIRA Issue

jira_create_issue

Create new JIRA issues by specifying project, type, summary, and optional details like description, assignee, and priority.

Instructions

Create a new JIRA issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesProject key
issueTypeYesIssue type (e.g., Bug, Task, Story)
summaryYesIssue summary
descriptionNoIssue description
assigneeNoAssignee account ID
priorityNoPriority name

Implementation Reference

  • The main handler function for the 'jira_create_issue' MCP tool. Constructs issue data from parameters and delegates to jiraClient.createIssue.
    async ({ project, issueType, summary, description, assignee, priority }) => {
      logger.info('Creating JIRA issue', { project, issueType, summary });
      try {
        const issueData = {
          project: { key: project },
          issuetype: { name: issueType },
          summary: summary,
        };
        
        if (description) issueData.description = description;
        if (assignee) issueData.assignee = { accountId: assignee };
        if (priority) issueData.priority = { name: priority };
    
        const createdIssue = await jiraClient.createIssue(issueData);
        logger.info('Successfully created issue', { 
          issueKey: createdIssue.key,
          summary 
        });
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(createdIssue, null, 2)
          }]
        };
      } catch (error) {
        logger.error('Failed to create issue', { project, summary, error: error.message });
        throw error;
      }
    }
  • Zod-based input schema defining parameters for creating a JIRA issue.
    inputSchema: {
      project: z.string().describe('Project key'),
      issueType: z.string().describe('Issue type (e.g., Bug, Task, Story)'),
      summary: z.string().describe('Issue summary'),
      description: z.string().optional().describe('Issue description'),
      assignee: z.string().optional().describe('Assignee account ID'),
      priority: z.string().optional().describe('Priority name')
  • server.js:251-295 (registration)
    Registration of the jira_create_issue tool with the MCP server, including metadata, schema, and handler.
    // Register jira_create_issue tool
    server.registerTool(
      'jira_create_issue',
      {
        title: 'Create JIRA Issue',
        description: 'Create a new JIRA issue',
        inputSchema: {
          project: z.string().describe('Project key'),
          issueType: z.string().describe('Issue type (e.g., Bug, Task, Story)'),
          summary: z.string().describe('Issue summary'),
          description: z.string().optional().describe('Issue description'),
          assignee: z.string().optional().describe('Assignee account ID'),
          priority: z.string().optional().describe('Priority name')
        }
      },
      async ({ project, issueType, summary, description, assignee, priority }) => {
        logger.info('Creating JIRA issue', { project, issueType, summary });
        try {
          const issueData = {
            project: { key: project },
            issuetype: { name: issueType },
            summary: summary,
          };
          
          if (description) issueData.description = description;
          if (assignee) issueData.assignee = { accountId: assignee };
          if (priority) issueData.priority = { name: priority };
    
          const createdIssue = await jiraClient.createIssue(issueData);
          logger.info('Successfully created issue', { 
            issueKey: createdIssue.key,
            summary 
          });
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(createdIssue, null, 2)
            }]
          };
        } catch (error) {
          logger.error('Failed to create issue', { project, summary, error: error.message });
          throw error;
        }
      }
    );
  • JiraClient.createIssue helper method that performs the actual API POST request to create the issue via JIRA REST API.
    async createIssue(issueData) {
      logger.info('Creating JIRA issue', { issueData });
      return await this.makeRequest('issue', {
        method: 'POST',
        body: JSON.stringify({ fields: issueData })
      });
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Create a new JIRA issue', which implies a write operation, but doesn't cover critical behaviors: whether it requires specific permissions, what happens on success/failure (e.g., returns an issue ID), if there are rate limits, or if it's idempotent. For a mutation tool with zero annotation coverage, this is a significant gap.

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 with zero waste: 'Create a new JIRA issue'. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary details. Every word earns its place.

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 (a mutation tool with 6 parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain return values (e.g., issue ID), error conditions, or behavioral nuances. For a creation tool with no structured output, the description should provide more context to be fully helpful.

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?

The schema description coverage is 100%, with all 6 parameters well-documented in the schema (e.g., 'Project key', 'Issue type'). The description adds no parameter information beyond what's in the schema. According to the rules, with high schema coverage (>80%), the baseline is 3 even with no param info in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create a new JIRA issue' clearly states the verb ('Create') and resource ('JIRA issue'), which is adequate. However, it doesn't distinguish this tool from its sibling 'jira_update_issue' (which also modifies issues) or specify what makes creation unique versus updating. The purpose is clear but lacks sibling differentiation.

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 project key), when not to use it (e.g., for existing issues), or refer to siblings like 'jira_update_issue' for modifications. Without any usage context, the agent must infer when this tool is 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/hackdonalds/jira-mcp'

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