Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

get_issue

Retrieve detailed information about a Jira issue including status, assignee, description, comments, and workflow data to check its current state before making updates.

Instructions

Retrieve detailed information about a specific Jira issue including status, assignee, description, comments, and workflow data. Use this to get current state before making updates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesIssue key (e.g., "PROJ-123") or numeric issue ID. This is the unique identifier for the issue.
expandNoComma-separated list of additional data: renderedFields,names,schema,transitions,operations,editmeta,changelog
fieldsNoSpecific fields to return (e.g., ["summary", "status", "assignee"]). If not specified, returns all fields.

Implementation Reference

  • Tool registration for 'get_issue' as part of createIssueTools() - defines name, description, and inputSchema with issueKey (required), expand, and fields parameters.
      name: 'get_issue',
      description: 'Retrieve detailed information about a specific Jira issue including status, assignee, description, comments, and workflow data. Use this to get current state before making updates.',
      inputSchema: {
        type: 'object',
        properties: {
          issueKey: {
            type: 'string',
            description: 'Issue key (e.g., "PROJ-123") or numeric issue ID. This is the unique identifier for the issue.',
          },
          expand: {
            type: 'string',
            description: 'Comma-separated list of additional data: renderedFields,names,schema,transitions,operations,editmeta,changelog',
          },
          fields: {
            type: 'array',
            items: { type: 'string' },
            description: 'Specific fields to return (e.g., ["summary", "status", "assignee"]). If not specified, returns all fields.',
          },
        },
        required: ['issueKey'],
      },
    },
  • Validation schema for get_issue: issueKey (required string), expand (optional string), fields (optional array of strings).
    export const getIssueSchema = yup.object({
      issueKey: yup.string().required('Issue key is required'),
      expand: yup.string().optional(),
      fields: yup.array().of(yup.string()).optional(),
    });
  • Handler for 'get_issue' tool in handleIssueTool(): validates args with getIssueSchema, calls jiraClient.getIssue(), then simplifies and returns issue data (summary, description, status, priority, assignee, reporter, project, issuetype, parent, subtasks, labels, components, etc.) as JSON.
    case 'get_issue': {
      const validatedArgs = await getIssueSchema.validate(args);
      const issue = await jiraClient.getIssue(validatedArgs);
    
      // Filter and simplify the issue data
      const simplifiedIssue = {
        id: issue.id,
        key: issue.key,
        self: issue.self,
        fields: {
          summary: issue.fields.summary,
          description: issue.fields.description,
          status: {
            id: issue.fields.status?.id,
            name: issue.fields.status?.name,
            statusCategory: {
              id: issue.fields.status?.statusCategory?.id,
              key: issue.fields.status?.statusCategory?.key,
              name: issue.fields.status?.statusCategory?.name
            }
          },
          priority: {
            id: issue.fields.priority?.id,
            name: issue.fields.priority?.name
          },
          assignee: issue.fields.assignee ? {
            accountId: issue.fields.assignee.accountId,
            displayName: issue.fields.assignee.displayName,
            emailAddress: issue.fields.assignee.emailAddress
          } : null,
          reporter: issue.fields.reporter ? {
            accountId: issue.fields.reporter.accountId,
            displayName: issue.fields.reporter.displayName,
            emailAddress: issue.fields.reporter.emailAddress
          } : null,
          creator: issue.fields.creator ? {
            accountId: issue.fields.creator.accountId,
            displayName: issue.fields.creator.displayName,
            emailAddress: issue.fields.creator.emailAddress
          } : null,
          project: {
            id: issue.fields.project?.id,
            key: issue.fields.project?.key,
            name: issue.fields.project?.name
          },
          issuetype: {
            id: issue.fields.issuetype?.id,
            name: issue.fields.issuetype?.name,
            subtask: issue.fields.issuetype?.subtask
          },
          parent: issue.fields.parent ? {
            id: issue.fields.parent.id,
            key: issue.fields.parent.key
          } : null,
          subtasks: issue.fields.subtasks?.map(subtask => ({
            id: subtask.id,
            key: subtask.key
          })) || [],
          labels: issue.fields.labels || [],
          components: issue.fields.components?.map(comp => ({
            id: comp.id,
            name: comp.name
          })) || [],
          fixVersions: issue.fields.fixVersions?.map(version => ({
            id: version.id,
            name: version.name,
            released: version.released
          })) || [],
          created: issue.fields.created,
          updated: issue.fields.updated,
          duedate: issue.fields.duedate,
          resolution: issue.fields.resolution,
          resolutiondate: issue.fields.resolutiondate
        }
      };
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(simplifiedIssue, null, 2),
          },
        ],
      };
    }
  • JiraClient.getIssue() method: calls the Jira API (jira.issues.getIssue) with issueIdOrKey, expand, and fields filters, returning a Promise<Issue>.
    async getIssue(input: GetIssueInput): Promise<Issue> {
      try {
        const response = await this.jira.issues.getIssue({
          issueIdOrKey: input.issueKey,
          expand: input.expand,
          fields: input.fields?.filter(field => field !== undefined) as string[],
        });
        return response as unknown as Issue;
      } catch (error) {
        throw new Error(`Failed to get issue: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • src/index.ts:71-77 (registration)
    Tool routing in main server: routes 'get_issue' (startsWith) to handleIssueTool() in the CallToolRequestSchema handler.
    } else if (
      name.startsWith('create_issue') ||
      name.startsWith('get_issue') ||
      name.startsWith('update_issue') ||
      name.startsWith('delete_issue')
    ) {
      return await handleIssueTool(name, args || {}, this.jiraClient);
Behavior3/5

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

No annotations exist, so description must cover behavioral traits. It correctly implies read-only via 'retrieve', but lacks explicit statements about side effects, authentication needs, or error handling. Adequate but not comprehensive.

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 core purpose, followed by actionable guidance. Every word contributes value.

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?

No output schema, but description hints at return content (status, assignee, etc.). Parameters are fully documented. Usage guideline is provided. For a simple read tool, this is nearly complete; could add a note about default field behavior.

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 the schema already explains parameters. The description adds minimal new meaning beyond listing example fields, which partially overlaps with the 'fields' parameter. Baseline score of 3 is appropriate.

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?

Description clearly states it retrieves detailed information about a specific Jira issue, listing example fields (status, assignee, etc.). This distinguishes it from mutation tools like create_issue, update_issue, and transition_issue.

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?

Explicitly advises using the tool to get current state before making updates, providing clear context. Could be improved by mentioning when not to use or suggesting alternatives for other operations.

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

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