Skip to main content
Glama
edrich13

MCP Jira Server

by edrich13

jira_get_issue

Retrieve complete details of any Jira issue using its issue key. Access summary, status, assignee, and more via the Jira REST API.

Instructions

Get details of a specific Jira issue by its key (e.g., PROJ-123)

Input Schema

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

Implementation Reference

  • Tool registration and input schema for jira_get_issue: defines the tool name, description, and input schema requiring 'issueKey' (a string like PROJ-123).
    const tools: Tool[] = [
      {
        name: 'jira_get_issue',
        description: 'Get details of a specific Jira issue by its key (e.g., PROJ-123)',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key (e.g., PROJ-123)',
            },
          },
          required: ['issueKey'],
        },
      },
  • Handler for jira_get_issue: extracts the issueKey argument, calls getJiraClient().getIssue(), and returns the issue data as JSON.
    case 'jira_get_issue': {
      const issue = await getJiraClient().getIssue(args.issueKey as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(issue, null, 2),
          },
        ],
      };
    }
  • src/index.ts:56-70 (registration)
    Part of the tools array registered via ListToolsRequestSchema handler (lines 313-317), making jira_get_issue available as an MCP tool.
    const tools: Tool[] = [
      {
        name: 'jira_get_issue',
        description: 'Get details of a specific Jira issue by its key (e.g., PROJ-123)',
        inputSchema: {
          type: 'object',
          properties: {
            issueKey: {
              type: 'string',
              description: 'The Jira issue key (e.g., PROJ-123)',
            },
          },
          required: ['issueKey'],
        },
      },
  • Actual Jira API call: JiraClient.getIssue() makes a GET request to /issue/{issueKey} in the Jira REST API v2 and returns the response data.
    async getIssue(issueKey: string): Promise<JiraIssue> {
      const response = await this.client.get(`/issue/${issueKey}`);
      return response.data;
    }
  • JiraIssue interface: Type definition for the issue object returned by getIssue(), including key, fields (summary, description, status, issuetype, priority, assignee, etc.).
    export interface JiraIssue {
      key: string;
      fields: {
        summary: string;
        description?: string;
        status: {
          name: string;
        };
        issuetype: {
          name: string;
        };
        priority?: {
          name: string;
        };
        assignee?: {
          displayName: string;
          emailAddress: string;
        };
        reporter?: {
          displayName: string;
          emailAddress: string;
        };
        created: string;
        updated: string;
        [key: string]: any;
      };
    }
Behavior2/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 only states 'get details' without disclosing it is a read-only operation, what fields are returned, or any behavioral traits. Minimal transparency.

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 no unnecessary words or repetition. It is appropriately front-loaded.

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

Completeness3/5

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

Given low complexity (1 param, no output schema), the description is minimally adequate but fails to mention what kind of details are returned. It is complete enough for a simple get, but could hint at response content.

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 coverage is 100% for the single parameter issueKey. The description adds an example format 'e.g., PROJ-123', which is helpful but does not significantly extend meaning beyond the schema. Baseline 3 due to high 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 verb 'get', the resource 'details of a specific Jira issue', and the identifier 'by its key (e.g., PROJ-123)'. This purpose distinguishes it from siblings like jira_search_issues or jira_get_comments.

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 lacks any guidance on when to use this tool vs. alternatives. It does not mention when to use other tools like jira_search_issues or any exclusions. The usage is only implied.

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

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