Skip to main content
Glama
hackdonalds

JIRA MCP Server

by hackdonalds

Get JIRA Issue

jira_get_issue

Retrieve detailed information about a specific JIRA issue using its issue key, enabling quick access to issue status, description, and related data for project management.

Instructions

Get details of a specific JIRA issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe JIRA issue key (e.g., PROJECT-123)

Implementation Reference

  • The inline handler function for the 'jira_get_issue' tool. It takes an issueKey, calls jiraClient.getIssue to fetch the issue data, formats it as JSON, and returns it in the MCP response format. Handles errors by logging and rethrowing.
    async ({ issueKey }) => {
      logger.info('Getting JIRA issue', { issueKey });
      try {
        const issue = await jiraClient.getIssue(issueKey);
        logger.info('Successfully retrieved issue', { issueKey });
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(issue, null, 2)
          }]
        };
      } catch (error) {
        logger.error('Failed to get issue', { issueKey, error: error.message });
        throw error;
      }
    }
  • The Zod input schema for the 'jira_get_issue' tool, specifying the required 'issueKey' parameter as a string with description.
    inputSchema: {
      issueKey: z.string().describe('The JIRA issue key (e.g., PROJECT-123)')
    }
  • server.js:191-216 (registration)
    The registration of the 'jira_get_issue' tool on the McpServer instance, including title, description, input schema, and the inline handler function.
    server.registerTool(
      'jira_get_issue',
      {
        title: 'Get JIRA Issue',
        description: 'Get details of a specific JIRA issue',
        inputSchema: {
          issueKey: z.string().describe('The JIRA issue key (e.g., PROJECT-123)')
        }
      },
      async ({ issueKey }) => {
        logger.info('Getting JIRA issue', { issueKey });
        try {
          const issue = await jiraClient.getIssue(issueKey);
          logger.info('Successfully retrieved issue', { issueKey });
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(issue, null, 2)
            }]
          };
        } catch (error) {
          logger.error('Failed to get issue', { issueKey, error: error.message });
          throw error;
        }
      }
    );
  • The JiraClient.getIssue helper method invoked by the tool handler. It logs the request and delegates to makeRequest to fetch the issue from the JIRA REST API endpoint `/rest/api/2/issue/{issueKey}`.
    async getIssue(issueKey) {
      logger.info('Getting JIRA issue', { issueKey });
      return await this.makeRequest(`issue/${issueKey}`);
    }
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 only states what the tool does ('Get details') without describing the return format, error handling, authentication needs, rate limits, or whether it's a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 that is front-loaded with the core purpose. There is no wasted language or unnecessary elaboration, making it highly efficient and easy to parse.

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 lack of annotations and output schema, the description is incomplete. It doesn't explain what details are returned, error conditions, or behavioral aspects like read-only nature. For a tool with no structured data beyond the input schema, the description should provide more context to be fully helpful.

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 schema description coverage is 100%, with the parameter 'issueKey' fully documented in the schema. The description doesn't add any additional meaning beyond what the schema provides (e.g., it doesn't explain the format of issue keys beyond the schema's example). With high schema coverage, the baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 verb ('Get details') and resource ('specific JIRA issue'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'jira_search' which might also retrieve issue information, missing the opportunity to specify this tool is for single-issue retrieval by key.

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. It doesn't mention that this is for retrieving a single issue by its key, as opposed to 'jira_search' for multiple issues or filtering, or when to prefer this over other read operations. No exclusions or prerequisites are stated.

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

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