Skip to main content
Glama

jira_get_create_meta

Retrieve required fields and allowed values for creating Jira issues in a specific project, ensuring proper issue setup by identifying mandatory inputs and dropdown options before submission.

Instructions

Get metadata for creating issues - shows required fields and allowed values (dropdown options) for a project and issue type. IMPORTANT: Call this before creating an issue to know what fields are required and what values are allowed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesProject key to get metadata for
issueTypeNoIssue type name to filter (e.g., Bug, Task, Story)

Implementation Reference

  • Core handler function that retrieves create metadata for a Jira project, fetching issue types and their field configurations including required fields and allowed values.
    async getCreateMeta(
      projectKey: string,
      issueTypeName?: string
    ): Promise<{
      projectKey: string;
      issueTypes: Array<{
        id: string;
        name: string;
        fields?: Array<{
          fieldId: string;
          name: string;
          required: boolean;
          hasAllowedValues: boolean;
          allowedValues?: Array<{ id: string; name: string; value?: string }>;
        }>;
      }>;
    }> {
      const issueTypesResult = await this.getCreateMetaIssueTypes(projectKey);
      const issueTypes = issueTypesResult.values;
    
      // Filter by issue type name if provided
      const filteredTypes = issueTypeName
        ? issueTypes.filter(
            (t) => t.name.toLowerCase() === issueTypeName.toLowerCase()
          )
        : issueTypes;
    
      // Get fields for each issue type
      const result = {
        projectKey,
        issueTypes: await Promise.all(
          filteredTypes.map(async (issueType) => {
            const fieldsResult = await this.getCreateMetaFields(
              projectKey,
              issueType.id
            );
            return {
              id: issueType.id,
              name: issueType.name,
              fields: fieldsResult.values.map((f) => ({
                fieldId: f.fieldId,
                name: f.name,
                required: f.required,
                hasAllowedValues: !!f.allowedValues,
                allowedValues: f.allowedValues,
              })),
            };
          })
        ),
      };
    
      return result;
    }
  • Zod schema defining input parameters for the jira_get_create_meta tool: projectKey (required) and optional issueType.
    const GetCreateMetaSchema = z.object({
      projectKey: z.string().describe("Project key to get metadata for"),
      issueType: z
        .string()
        .optional()
        .describe("Issue type name to filter (e.g., Bug, Task, Story)"),
    });
  • src/index.ts:456-474 (registration)
    Tool registration in the list of available tools, including name, description, and input schema.
    {
      name: "jira_get_create_meta",
      description:
        "Get metadata for creating issues - shows required fields and allowed values (dropdown options) for a project and issue type. IMPORTANT: Call this before creating an issue to know what fields are required and what values are allowed.",
      inputSchema: {
        type: "object",
        properties: {
          projectKey: {
            type: "string",
            description: "Project key to get metadata for",
          },
          issueType: {
            type: "string",
            description: "Issue type name to filter (e.g., Bug, Task, Story)",
          },
        },
        required: ["projectKey"],
      },
    },
  • Helper method to fetch available issue types for create meta in a project via Jira API.
    async getCreateMetaIssueTypes(projectKey: string): Promise<{
      values: Array<{
        id: string;
        name: string;
        description: string;
        subtask: boolean;
      }>;
      total: number;
    }> {
      return this.request<{
        values: Array<{
          id: string;
          name: string;
          description: string;
          subtask: boolean;
        }>;
        total: number;
      }>(`/issue/createmeta/${projectKey}/issuetypes`);
    }
  • Helper method to fetch field metadata (required, allowed values) for a specific issue type in create meta context.
    async getCreateMetaFields(
      projectKey: string,
      issueTypeId: string
    ): Promise<{
      values: Array<{
        fieldId: string;
        name: string;
        required: boolean;
        allowedValues?: Array<{ id: string; name: string; value?: string }>;
        schema: { type: string; system?: string; custom?: string };
        defaultValue?: unknown;
      }>;
      total: number;
    }> {
      return this.request<{
        values: Array<{
          fieldId: string;
          name: string;
          required: boolean;
          allowedValues?: Array<{ id: string; name: string; value?: string }>;
          schema: { type: string; system?: string; custom?: string };
          defaultValue?: unknown;
        }>;
        total: number;
      }>(
        `/issue/createmeta/${projectKey}/issuetypes/${issueTypeId}?maxResults=100`
      );
    }
Behavior3/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 explains that the tool retrieves metadata (a read-only operation) and provides context about its purpose in issue creation workflows. However, it lacks details on potential rate limits, authentication needs, or error conditions, which would be helpful for a tool with no annotation coverage.

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 concise and well-structured, consisting of two sentences that efficiently convey purpose and usage guidelines. Every sentence adds value, with no wasted words, making it easy for an agent to parse and understand quickly.

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?

For a tool with no annotations and no output schema, the description provides good contextual completeness. It explains what the tool does, when to use it, and its role relative to other tools. However, it could improve by hinting at the output structure (e.g., mentioning it returns metadata fields) to compensate for the lack of output schema.

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 input schema has 100% description coverage, with clear parameter descriptions in the schema itself. The description adds minimal semantic context beyond the schema, mentioning 'project and issue type' but not elaborating on parameter usage. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema does most of the work.

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: 'Get metadata for creating issues - shows required fields and allowed values (dropdown options) for a project and issue type.' It uses specific verbs ('get metadata', 'shows') and resources ('issues', 'fields', 'values'), and distinguishes itself from siblings like jira_create_issue by focusing on metadata retrieval rather than issue creation.

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: 'IMPORTANT: Call this before creating an issue to know what fields are required and what values are allowed.' This clearly indicates when to use the tool (before creating an issue) and implies an alternative (jira_create_issue), helping the agent understand its role in the workflow.

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