Skip to main content
Glama

jira_get_issue

Retrieve detailed information about a specific Jira issue using its unique key, enabling users to access issue data and expanded fields for project management and tracking.

Instructions

Get details of a Jira issue by its key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key (e.g., PROJ-123)
expandNoFields to expand

Implementation Reference

  • MCP tool handler in the CallToolRequestHandler switch statement. Validates input using GetIssueSchema, calls jiraClient.getIssue(), and returns the issue as JSON text.
    case "jira_get_issue": {
      const { issueKey, expand } = GetIssueSchema.parse(args);
      const issue = await jiraClient.getIssue(issueKey, expand);
      return {
        content: [{ type: "text", text: JSON.stringify(issue, null, 2) }],
      };
    }
  • Zod schema used for input validation in the tool handler.
    const GetIssueSchema = z.object({
      issueKey: z.string().describe("The Jira issue key (e.g., PROJ-123)"),
      expand: z.array(z.string()).optional().describe("Fields to expand"),
    });
  • src/index.ts:211-229 (registration)
    Tool registration in ListToolsRequestHandler, including JSON input schema for MCP client discovery.
    {
      name: "jira_get_issue",
      description: "Get details of a Jira issue by its key",
      inputSchema: {
        type: "object",
        properties: {
          issueKey: {
            type: "string",
            description: "The Jira issue key (e.g., PROJ-123)",
          },
          expand: {
            type: "array",
            items: { type: "string" },
            description: "Fields to expand",
          },
        },
        required: ["issueKey"],
      },
    },
  • Core implementation in JiraClient class that performs the HTTP request to Jira REST API to fetch the issue details.
    async getIssue(issueKey: string, expand?: string[]): Promise<JiraIssue> {
      const params = expand ? `?expand=${expand.join(",")}` : "";
      return this.request<JiraIssue>(`/issue/${issueKey}${params}`);
    }
  • TypeScript interface defining the structure of a JiraIssue returned by the API.
    export interface JiraIssue {
      id: string;
      key: string;
      self: string;
      fields: {
        summary: string;
        description?: string;
        status: {
          name: string;
          id: string;
        };
        priority?: {
          name: string;
          id: string;
        };
        assignee?: {
          displayName: string;
          emailAddress: string;
          name: string;
        };
        reporter?: {
          displayName: string;
          emailAddress: string;
          name: string;
        };
        created: string;
        updated: string;
        issuetype: {
          name: string;
          id: string;
        };
        project: {
          key: string;
          name: string;
        };
        labels?: string[];
        components?: Array<{ name: string }>;
        fixVersions?: Array<{ name: string }>;
        [key: string]: unknown;
      };
    }
Behavior2/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 states the tool retrieves issue details but doesn't mention whether it requires authentication, rate limits, what details are included (e.g., fields, comments), or error handling. This leaves significant gaps for a read operation in a complex system like Jira.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core purpose and efficiently communicates the essential action without unnecessary elaboration, making it easy for an agent to parse quickly.

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 the complexity of Jira issues and the lack of annotations and output schema, the description is insufficient. It doesn't explain what 'details' include, potential authentication needs, or how results are structured. For a tool in a rich API environment with many sibling tools, more context is needed to guide effective use.

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 description mentions retrieving details 'by its key', which aligns with the 'issueKey' parameter in the schema. However, with 100% schema description coverage, the schema already fully documents both parameters ('issueKey' and 'expand'), so the description adds minimal value beyond reinforcing the primary parameter. No additional semantic context is provided.

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 ('Get details') and resource ('Jira issue by its key'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'jira_search_issues' or 'jira_get_comments', but the specificity of retrieving a single issue by key is reasonably distinct from those 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?

The description provides no guidance on when to use this tool versus alternatives like 'jira_search_issues' for multiple issues or 'jira_get_comments' for comment-specific details. It lacks any mention of prerequisites, context, or exclusions, leaving the agent to infer usage based on the name alone.

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