Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

create_issue

Create a new Jira issue by specifying the project, summary, and description to manage tasks or bugs.

Instructions

Create an issue in Jira

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyOrIdYesThe key or ID of the project
summaryYesThe summary of the issue
descriptionYesThe description of the issue

Implementation Reference

  • The main handler function that creates a Jira issue via POST to /rest/api/2/issue. Builds a payload with project key, issue type (Task), summary, and description, then calls $jiraJson to make the HTTP request.
    export async function createIssue(input: CreateIssueInput) {
      const url = new URL(`/rest/api/2/issue`, env.JIRA_BASE_URL);
    
      const payload = {
        fields: {
          project: { key: input.projectKeyOrId },
          issuetype: { name: ISSUE_TYPES.TASK },
          summary: input.summary,
          description: input.description,
        },
      };
    
      const json = await $jiraJson(url.toString(), {
        method: "POST",
        body: JSON.stringify(payload),
      });
    
      if (json.isErr()) return err(json.error);
    
      return ok(json.value);
    }
  • Zod schema defining the input for create_issue: projectKeyOrId (string), summary (string), description (string).
    export const createIssueInputSchema = z.object({
      projectKeyOrId: z.string().describe("The key or ID of the project"),
      summary: z.string().describe("The summary of the issue"),
      description: z.string().describe("The description of the issue"),
    });
  • src/app.ts:28-48 (registration)
    Imports CREATE_ISSUE_TOOL, createIssue, and createIssueInputSchema from create-issue.ts, and registers the tool in the tools array at line 47.
    import {
      CREATE_ISSUE_TOOL,
      createIssue,
      createIssueInputSchema,
    } from "./tools/create-issue.js";
    
    const server = new Server(
      { name: "Jira MCP Server", version: VERSION },
      { capabilities: { tools: {} } },
    );
    
    export const tools = [
      // list
      LIST_PROJECTS_TOOL,
      LIST_BOARDS_TOOL,
      LIST_SPRINTS_FROM_BOARD_TOOL,
      LIST_ISSUES_FROM_SPRINT_TOOL,
    
      // create
      CREATE_ISSUE_TOOL,
    ] satisfies Tool[];
  • src/app.ts:169-194 (registration)
    The tool call handler in app.ts that routes 'create_issue' to validate input via createIssueInputSchema.safeParse and execute the createIssue function.
    if (name === CREATE_ISSUE_TOOL.name) {
      const input = createIssueInputSchema.safeParse(args);
    
      if (!input.success) {
        return {
          isError: true,
          content: [{ type: "text", text: "Invalid input" }],
        };
      }
    
      const result = await createIssue(input.data);
    
      if (result.isErr()) {
        console.error(result.error.message);
        return {
          isError: true,
          content: [{ type: "text", text: "An error occurred" }],
        };
      }
    
      return {
        content: [
          { type: "text", text: JSON.stringify(result.value, null, 2) },
        ],
      };
    }
  • The $jiraJson helper function used by createIssue to make authenticated HTTP requests to the Jira API and parse JSON responses.
    export async function $jiraJson(url: string, options?: RequestInit) {
      try {
        const response = await $jira(url, options);
    
        if (response.isErr()) return err(response.error);
    
        const json = await response.value.json();
    
        return ok(json);
      } catch (error) {
        return err(new Error(`Failed to fetch ${url}: ${error}`));
      }
    }
Behavior2/5

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

No annotations provided, so description carries full burden. Only states it creates an issue; does not disclose side effects, permissions needed, success/failure behavior, or whether the action is idempotent.

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?

Extremely concise single sentence with no filler; every word is essential.

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 no output schema and no annotations, the description should hint at return value or additional behavior. It does not; leaves agent guessing about what happens after creation.

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%, so baseline is 3. Description adds no extra semantic context beyond the schema definitions; e.g., does not explain the purpose of projectKeyOrId or summary.

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

Purpose5/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 the resource ('an issue in Jira'), which is distinct from sibling tools that are all list operations.

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 on when to use versus alternatives (e.g., list_issues_from_sprint). Does not mention prerequisites such as having a project key or that summary and description are required.

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/ParasSolanki/jira-mcp-server'

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