Skip to main content
Glama
KS-GEN-AI

Jira MCP Server

by KS-GEN-AI

create_ticket

Create Jira tickets by specifying project, summary, description, and issue type to track tasks, bugs, or features in your workflow.

Instructions

Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYes
summaryYesThe summary of the ticket
descriptionYesThe description of the ticket
issuetypeYes
parentNoThe key of the parent ticket (the epic)

Implementation Reference

  • Core handler function that creates a Jira ticket by making a POST request to /rest/api/3/issue with the provided project key, summary, description (in ADF format), issue type name, and optional parent key.
    async function createTicket(
      project: string,
      summary: string,
      description: string,
      issuetype: string,
      parentID?: string,
    ): Promise<any> {
      try {
        const jiraDescription = {
          type: 'doc',
          version: 1,
          content: [
            {
              type: 'paragraph',
              content: [
                {
                  type: 'text',
                  text: description,
                },
              ],
            },
          ],
        };
    
        //parent is somethng like "parent": {"key": "SCRUM-19"}
        const parent = parentID ? { key: parentID } : undefined;
    
        const response = await axios.post(
          `${JIRA_URL}/rest/api/3/issue`,
          {
            fields: {
              project: {
                key: project,
              },
              summary,
              description: description ? jiraDescription : undefined,
              issuetype: {
                name: issuetype,
              },
              parent,
            },
          },
          {
            headers: getAuthHeaders().headers,
          },
        );
    
        return response.data;
      } catch (error: any) {
        return {
          error: error.response.data,
        };
      }
    }
  • src/index.ts:81-123 (registration)
    Tool registration in the MCP tools list, including name, description, and input schema.
    {
      name: 'create_ticket',
      description:
        'Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field.',
      inputSchema: {
        type: 'object',
        properties: {
          project: {
            type: 'object',
            properties: {
              key: {
                type: 'string',
                description: 'The project key',
              },
            },
            required: ['key'],
          },
          summary: {
            type: 'string',
            description: 'The summary of the ticket',
          },
          description: {
            type: 'string',
            description: 'The description of the ticket',
          },
          issuetype: {
            type: 'object',
            properties: {
              name: {
                type: 'string',
                description: 'The name of the issue type',
              },
            },
            required: ['name'],
          },
          parent: {
            type: 'string',
            description: 'The key of the parent ticket (the epic)',
          },
        },
        required: ['project', 'summary', 'description', 'issuetype'],
      },
    },
  • Input schema defining the parameters for the create_ticket tool: project (with key), summary, description, issuetype (with name), optional parent.
    inputSchema: {
      type: 'object',
      properties: {
        project: {
          type: 'object',
          properties: {
            key: {
              type: 'string',
              description: 'The project key',
            },
          },
          required: ['key'],
        },
        summary: {
          type: 'string',
          description: 'The summary of the ticket',
        },
        description: {
          type: 'string',
          description: 'The description of the ticket',
        },
        issuetype: {
          type: 'object',
          properties: {
            name: {
              type: 'string',
              description: 'The name of the issue type',
            },
          },
          required: ['name'],
        },
        parent: {
          type: 'string',
          description: 'The key of the parent ticket (the epic)',
        },
      },
      required: ['project', 'summary', 'description', 'issuetype'],
    },
  • MCP request handler case for 'create_ticket' that validates arguments and calls the createTicket function, returning the response as text content.
    case 'create_ticket': {
      const project: any = request.params.arguments?.project;
      const summary: any = request.params.arguments?.summary;
      const description: any = request.params.arguments?.description;
      const issuetype: any = request.params.arguments?.issuetype;
      const parent: any = request.params.arguments?.parent;
    
      if (!project || !summary || !description || !issuetype) {
        throw new Error(
          'Project, summary, description and issuetype are required',
        );
      }
    
      try {
        const response = await createTicket(
          project.key,
          summary,
          description,
          issuetype.name,
          parent,
        );
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(response, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(error.response.data, null, 2),
            },
          ],
        };
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool creates a ticket (implying a write/mutation operation) and mentions the markdown restriction, but lacks critical details like required permissions, whether the operation is idempotent, error handling, or what happens on success (e.g., returns ticket ID). For a mutation tool with zero annotation coverage, this is insufficient.

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

Conciseness4/5

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

The description is brief (two sentences) and front-loaded with the core purpose. The second sentence about markdown is relevant but could be more integrated. No wasted words, though it could be slightly more structured (e.g., separating constraints from the main action).

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, no output schema, and 60% schema coverage, the description is incomplete. It lacks information on authentication needs, error cases, return values, and how to handle the 'parent' parameter (optional but semantically important). The markdown hint is useful but insufficient for full context.

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 60% (3 of 5 parameters have descriptions in schema: project.key, summary, description). The description adds no parameter-specific information beyond the markdown restriction, which applies to all fields but doesn't clarify individual parameters. With moderate schema coverage, the baseline is 3 as the description doesn't compensate for the coverage gap nor add meaningful semantics.

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 a ticket') and target system ('on Jira'), with the specific API endpoint '/rest/api/3/issue' providing technical context. However, it doesn't distinguish this from sibling tools like 'edit_ticket' or 'delete_ticket' beyond the creation aspect, missing explicit 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 like 'edit_ticket' or 'assign_ticket'. It mentions 'Do not use markdown in any field' as a constraint, but this is a formatting rule rather than usage context. No prerequisites, dependencies, or comparison to siblings are included.

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/KS-GEN-AI/jira-mcp-server'

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