Skip to main content
Glama

jira_get_create_meta

Retrieve required and available fields for creating Jira issues by project and issue type. Call before creating an issue to know exactly what data each issue type needs.

Instructions

Get metadata about fields required and available when creating issues in a project. Returns simplified field rows (id, type, operations, allowedValues) per issue type — the same shape as jira_get_edit_meta. Call this before jira_create_issue to understand what data is needed for each issue type.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectKey": "<projectKey>"
    },
    "name": "jira_get_create_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
issueTypesNoOptional: limit results to specific issue types (e.g., ["Bug", "Task"])
projectKeyYesProject key to get create metadata for (e.g., KP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it discloses the return payload (simplified field rows with id, type, operations, allowedValues) and implies read-only behavior via 'Get'. It does not mention permission requirements or behavior when a project key is invalid.

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?

Two sentences, front-loaded with the purpose, then the return shape, then the prerequisite call. Nothing is redundant or padded.

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 simple two-parameter read tool with no output schema, the description covers purpose, return shape, and workflow position well enough to call it confidently. Minor gaps around auth/permission expectations and error behavior keep it short of full completeness.

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 both parameters are already documented in the schema, and the baseline is 3. The description reinforces that results are per issue type, which clarifies the meaning of the issueTypes filter, but adds no format or syntax detail beyond the schema.

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?

States a specific verb and resource: get metadata about fields required and available when creating issues in a project. The scope qualifier 'when creating' distinguishes it from jira_get_edit_meta, and it names that sibling explicitly for shape comparison.

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

Usage Guidelines4/5

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

Gives an explicit call-order instruction: 'Call this before jira_create_issue to understand what data is needed.' That is clear when-to-use guidance tied to a named sibling. It does not address a when-not case, such as using jira_get_edit_meta instead for updates.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.