Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

get_issue_types

Retrieve all issue types for a Jira project, including names, IDs, descriptions, and workflows. Use this before creating issues to get valid issueType values.

Instructions

Get all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyYesThe project key (e.g., "PROJ") or numeric project ID. Use get_projects to find available project keys.

Implementation Reference

  • Handler for the 'get_issue_types' tool. Validates args using getIssueTypesSchema, calls jiraClient.getIssueTypes(), and returns essential issue type fields (id, name, desc, subtask, level).
    case 'get_issue_types': {
      const validatedArgs = await getIssueTypesSchema.validate(args);
      const issueTypes = await jiraClient.getIssueTypes(validatedArgs);
    
      // Extract essential fields, remove iconUrl, improve text syntax
      const essentialTypes = issueTypes?.map((type) => ({
        id: type.id,
        name: type.name,
        desc: type.description, // Shorter field name
        subtask: type.subtask,
        level: type.hierarchyLevel // Shorter field name
      }));
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(essentialTypes, null, 2),
          },
        ],
      };
  • Schema definition for get_issue_types input: requires a 'projectKey' string.
    export const getIssueTypesSchema = yup.object({
      projectKey: yup.string().required('Project key is required'),
    });
  • TypeScript type alias GetIssueTypesInput inferred from the schema.
    export type GetIssueTypesInput = yup.InferType<typeof getIssueTypesSchema>;
  • Registration of the 'get_issue_types' tool: defines name, description, and inputSchema (requiring projectKey).
      name: 'get_issue_types',
      description: 'Get all available issue types (Bug, Story, Task, Epic, etc.) for a specific project. Returns type names, IDs, descriptions, and workflow information. Required before creating issues to know valid issueType values.',
      inputSchema: {
        type: 'object',
        properties: {
          projectKey: {
            type: 'string',
            description: 'The project key (e.g., "PROJ") or numeric project ID. Use get_projects to find available project keys.',
          },
        },
        required: ['projectKey'],
      },
    },
  • src/index.ts:69-70 (registration)
    Routing registration: tool names starting with 'get_issue_types' are dispatched to handleProjectTool.
    if (name.startsWith('get_projects') || name.startsWith('get_issue_types')) {
      return await handleProjectTool(name, args || {}, this.jiraClient);
  • JiraClient.getIssueTypes() method that calls the Jira API with projectIdOrKey and expand='issueTypes', returning the issue types list.
    // Get issue types for a project
    async getIssueTypes(input: GetIssueTypesInput) {
      try {
        const response = await this.jira.projects.getProject({
          projectIdOrKey: input.projectKey,
          expand: 'issueTypes',
        });
        return response.issueTypes;
      } catch (error) {
        throw new Error(`Failed to get issue types: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
Behavior4/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. It states 'Returns type names, IDs, descriptions, and workflow information', clearly implying a read-only operation with no side effects. This is sufficiently transparent for a simple retrieval tool.

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 two sentences with no wasted words. The first sentence states the primary purpose, and the second adds return information and usage guidance. It is front-loaded and efficient.

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

Completeness5/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description covers purpose, when to use, and what it returns. It is fully adequate for an AI agent to select and invoke the tool correctly.

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 input schema has 100% coverage, so the baseline is 3. The schema itself already contains a helpful description for projectKey, including an example and cross-reference to get_projects. The tool description adds no additional parameter detail beyond 'for a specific project', which is already implied.

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 'Get all available issue types for a specific project' and mentions typical types (Bug, Story, Task, Epic). It distinguishes from siblings by noting it's required before creating issues, making it clear what the tool does.

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?

The description explicitly says 'Required before creating issues to know valid issueType values', providing clear context for when to use the tool. However, it does not state when not to use it or mention alternatives, which would improve the score.

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