Skip to main content
Glama
cosmix

JIRA MCP Server

by cosmix

create_issue

Create a new JIRA issue by specifying project key, issue type, summary, description, and additional fields to track work items.

Instructions

Create a new JIRA issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesThe project key where the issue will be created
issueTypeYesThe type of issue to create (e.g., "Bug", "Story", "Task")
summaryYesThe issue summary/title
descriptionNoThe issue description
fieldsNoAdditional fields to set on the issue

Implementation Reference

  • MCP CallToolRequest handler case for 'create_issue': validates input parameters and delegates to JiraApiService.createIssue method, returning the created issue as JSON text content.
    case "create_issue": {
      // Basic validation
      if (
        !args.projectKey ||
        typeof args.projectKey !== "string" ||
        !args.issueType ||
        typeof args.issueType !== "string" ||
        !args.summary ||
        typeof args.summary !== "string"
      ) {
        throw new McpError(
          ErrorCode.InvalidParams,
          "projectKey, issueType, and summary are required",
        );
      }
      const response = await this.jiraApi.createIssue(
        args.projectKey,
        args.issueType,
        args.summary,
        args.description as string | undefined,
        args.fields as Record<string, any> | undefined,
      );
      return {
        content: [
          { type: "text", text: JSON.stringify(response, null, 2) },
        ],
      };
    }
  • Input schema definition for the 'create_issue' tool, specifying required fields (projectKey, issueType, summary) and optional fields (description, fields).
    inputSchema: {
      type: "object",
      properties: {
        projectKey: {
          type: "string",
          description: "The project key where the issue will be created",
        },
        issueType: {
          type: "string",
          description:
            'The type of issue to create (e.g., "Bug", "Story", "Task")',
        },
        summary: {
          type: "string",
          description: "The issue summary/title",
        },
        description: {
          type: "string",
          description: "The issue description",
        },
        fields: {
          type: "object",
          description: "Additional fields to set on the issue",
          additionalProperties: true,
        },
      },
      required: ["projectKey", "issueType", "summary"],
      additionalProperties: false,
    },
  • src/index.ts:131-163 (registration)
    Tool registration in ListTools response: defines name, description, and inputSchema for 'create_issue'.
    {
      name: "create_issue",
      description: "Create a new JIRA issue",
      inputSchema: {
        type: "object",
        properties: {
          projectKey: {
            type: "string",
            description: "The project key where the issue will be created",
          },
          issueType: {
            type: "string",
            description:
              'The type of issue to create (e.g., "Bug", "Story", "Task")',
          },
          summary: {
            type: "string",
            description: "The issue summary/title",
          },
          description: {
            type: "string",
            description: "The issue description",
          },
          fields: {
            type: "object",
            description: "Additional fields to set on the issue",
            additionalProperties: true,
          },
        },
        required: ["projectKey", "issueType", "summary"],
        additionalProperties: false,
      },
    },
  • Core implementation of issue creation: constructs payload with project, summary, issue type, optional description/fields, and performs POST request to JIRA REST API /rest/api/3/issue.
    async createIssue(
      projectKey: string,
      issueType: string,
      summary: string,
      description?: string,
      fields?: Record<string, any>
    ): Promise<{ id: string; key: string }> {
      const payload = {
        fields: {
          project: {
            key: projectKey,
          },
          summary,
          issuetype: {
            name: issueType,
          },
          ...(description && { description }),
          ...fields,
        },
      };
    
      return this.fetchJson<{ id: string; key: string }>("/rest/api/3/issue", {
        method: "POST",
        body: JSON.stringify(payload),
      });
    }
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. 'Create a new JIRA issue' implies a write operation but reveals nothing about authentication requirements, rate limits, side effects, error conditions, or what happens on success. 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 that states the core purpose without unnecessary words. It's appropriately sized for a straightforward creation tool and gets directly to the point.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is inadequate. It doesn't address what the tool returns, error handling, or behavioral characteristics. The agent would need to guess about important operational aspects.

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 description adds no parameter information beyond what's already in the schema (which has 100% coverage). It doesn't explain relationships between parameters, provide examples, or clarify the 'fields' object's purpose. With complete schema documentation, the baseline is 3, but the description contributes no additional value.

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 verb ('Create') and resource ('new JIRA issue'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'update_issue' or explain how creation differs from modification, which prevents 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 like 'update_issue' or 'search_issues'. There's no mention of prerequisites, constraints, or typical use cases, leaving the agent to infer usage context from the tool name 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/cosmix/jira-mcp'

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