Skip to main content
Glama

jira_create_issue_advanced

Create detailed Jira issues with comprehensive field support including fixVersions, components, and custom fields. Use jira_get_create_meta first to discover required fields and allowed values for accurate issue creation.

Instructions

Create a new Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_create_meta first to discover required fields and allowed values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesProject key
summaryYesIssue summary
issueTypeYesIssue type (e.g., Bug, Task, Story)
descriptionNoIssue description
priorityNoPriority name
assigneeNoAssignee username
reporterNoReporter username
labelsNoLabels
componentsNoComponent names
fixVersionsNoFix version names
affectsVersionsNoAffects version names
customFieldsNoCustom fields as key-value pairs (e.g., {"customfield_10001": "value"})

Implementation Reference

  • MCP tool handler for jira_create_issue_advanced: validates input with schema, constructs fields object handling optional fields like components, versions, customFields, and calls jiraClient.createIssueRaw to create the issue
    case "jira_create_issue_advanced": {
      const {
        projectKey,
        summary,
        issueType,
        description,
        priority,
        assignee,
        reporter,
        labels,
        components,
        fixVersions,
        affectsVersions,
        customFields,
      } = CreateIssueAdvancedSchema.parse(args);
    
      const fields: Record<string, unknown> = {
        project: { key: projectKey },
        summary,
        issuetype: { name: issueType },
      };
    
      if (description) fields.description = description;
      if (priority) fields.priority = { name: priority };
      if (assignee) fields.assignee = { name: assignee };
      if (reporter) fields.reporter = { name: reporter };
      if (labels) fields.labels = labels;
      if (components)
        fields.components = components.map((name) => ({ name }));
      if (fixVersions)
        fields.fixVersions = fixVersions.map((name) => ({ name }));
      if (affectsVersions)
        fields.versions = affectsVersions.map((name) => ({ name }));
    
      // Merge custom fields
      if (customFields) {
        Object.assign(fields, customFields);
      }
    
      const issue = await jiraClient.createIssueRaw(fields);
      return {
        content: [{ type: "text", text: JSON.stringify(issue, null, 2) }],
      };
    }
  • Zod input schema validation for jira_create_issue_advanced tool parameters
    const CreateIssueAdvancedSchema = z.object({
      projectKey: z.string().describe("Project key"),
      summary: z.string().describe("Issue summary"),
      issueType: z.string().describe("Issue type (e.g., Bug, Task, Story)"),
      description: z.string().optional().describe("Issue description"),
      priority: z.string().optional().describe("Priority name"),
      assignee: z.string().optional().describe("Assignee username"),
      reporter: z.string().optional().describe("Reporter username"),
      labels: z.array(z.string()).optional().describe("Labels"),
      components: z.array(z.string()).optional().describe("Component names"),
      fixVersions: z.array(z.string()).optional().describe("Fix version names"),
      affectsVersions: z
        .array(z.string())
        .optional()
        .describe("Affects version names"),
      customFields: z
        .record(z.unknown())
        .optional()
        .describe(
          'Custom fields as key-value pairs (e.g., {"customfield_10001": "value"})'
        ),
    });
  • src/index.ts:555-600 (registration)
    Tool registration in ListTools handler including name, description, and inputSchema
    {
      name: "jira_create_issue_advanced",
      description:
        "Create a new Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_create_meta first to discover required fields and allowed values.",
      inputSchema: {
        type: "object",
        properties: {
          projectKey: { type: "string", description: "Project key" },
          summary: { type: "string", description: "Issue summary" },
          issueType: {
            type: "string",
            description: "Issue type (e.g., Bug, Task, Story)",
          },
          description: { type: "string", description: "Issue description" },
          priority: { type: "string", description: "Priority name" },
          assignee: { type: "string", description: "Assignee username" },
          reporter: { type: "string", description: "Reporter username" },
          labels: {
            type: "array",
            items: { type: "string" },
            description: "Labels",
          },
          components: {
            type: "array",
            items: { type: "string" },
            description: "Component names",
          },
          fixVersions: {
            type: "array",
            items: { type: "string" },
            description: "Fix version names",
          },
          affectsVersions: {
            type: "array",
            items: { type: "string" },
            description: "Affects version names",
          },
          customFields: {
            type: "object",
            description:
              'Custom fields as key-value pairs (e.g., {"customfield_10001": "value"})',
          },
        },
        required: ["projectKey", "summary", "issueType"],
      },
    },
  • JiraClient helper method that performs the raw POST /issue API call used by the advanced create issue handler
    async createIssueRaw(fields: Record<string, unknown>): Promise<JiraIssue> {
      return this.request<JiraIssue>("/issue", {
        method: "POST",
        body: JSON.stringify({ fields }),
      });
    }
Behavior3/5

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

No annotations are provided, so the description carries full burden. It indicates this is a creation/mutation tool ('Create a new Jira issue'), implying it modifies data. However, it lacks details on permissions needed, error handling, or response format. The mention of 'full field support' hints at complexity but doesn't describe behavioral traits like validation rules or side effects.

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 two concise sentences that are front-loaded with the core purpose and followed by a critical usage guideline. Every word earns its place with no redundancy or fluff, making it highly efficient and well-structured for an agent.

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

Completeness4/5

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

Given the tool's complexity (12 parameters, mutation operation) and lack of annotations/output schema, the description is reasonably complete. It covers the purpose and critical prerequisite, but could better address behavioral aspects like what happens on success/failure. The high schema coverage helps compensate for some gaps.

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 the schema already documents all 12 parameters thoroughly. The description adds minimal value beyond the schema by mentioning 'fixVersions, components, and custom fields' as examples, but doesn't provide additional syntax, format, or semantic context. This meets the baseline for high schema coverage.

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 tool's purpose: 'Create a new Jira issue with full field support including fixVersions, components, and custom fields.' It specifies the verb ('Create'), resource ('new Jira issue'), and scope ('full field support'), distinguishing it from the simpler 'jira_create_issue' sibling tool by emphasizing advanced capabilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance: 'Use jira_get_create_meta first to discover required fields and allowed values.' This tells the agent when to use this tool (after metadata discovery) and references a specific alternative/sibling tool for prerequisite information, which is optimal guidance.

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/yogeshhrathod/JiraMCP'

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