Skip to main content
Glama
Dsazz

JIRA MCP Server

jira_get_boards

Retrieve accessible JIRA boards with filtering by type, project, and name to manage agile workflows and project organization.

Instructions

Get all accessible JIRA boards with filtering by type, project, and name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
startAtNo
maxResultsNo
typeNo
nameNo
projectKeyOrIdNo
accountIdLocationNo
projectLocationNo
includePrivateNo
negateLocationFilteringNo
orderByNo
expandNo
filterIdNo

Implementation Reference

  • GetBoardsHandler class: core implementation of the jira_get_boards tool logic, including parameter validation, use case execution, response formatting, and comprehensive error handling.
    export class GetBoardsHandler extends BaseToolHandler<GetBoardsParams, string> {
      private boardListFormatter: BoardListFormatter;
    
      /**
       * Create a new GetBoardsHandler with use case and validator
       *
       * @param getBoardsUseCase - Use case for retrieving boards
       * @param boardValidator - Validator for board parameters
       */
      constructor(
        private readonly getBoardsUseCase: GetBoardsUseCase,
        private readonly boardValidator: BoardValidator,
      ) {
        super("JIRA", "Get Boards");
        this.boardListFormatter = new BoardListFormatter();
      }
    
      /**
       * Execute the handler logic
       * Retrieves JIRA boards with optional filtering and formatting
       *
       * @param params - Parameters for board retrieval
       */
      protected async execute(params: GetBoardsParams): Promise<string> {
        try {
          // Step 1: Validate parameters
          const validatedParams =
            this.boardValidator.validateGetBoardsParams(params);
          this.logger.info("Getting JIRA boards");
    
          // Step 2: Get boards using use case
          this.logger.debug("Retrieving boards with params:", {
            hasType: !!validatedParams.type,
            hasProject: !!validatedParams.projectKeyOrId,
            hasName: !!validatedParams.name,
            maxResults: validatedParams.maxResults,
          });
    
          const boards = await this.getBoardsUseCase.execute(validatedParams);
    
          // Step 3: Format and return success response
          this.logger.info(`Successfully retrieved ${boards.length} boards`);
          return this.boardListFormatter.format({
            boards,
            appliedFilters: {
              type: validatedParams.type,
              projectKeyOrId: validatedParams.projectKeyOrId,
              name: validatedParams.name,
            },
          });
        } catch (error) {
          this.logger.error(`Failed to get JIRA boards: ${error}`);
          throw this.enhanceError(error, params);
        }
      }
    
      /**
       * Enhance error messages for better user guidance
       */
      private enhanceError(error: unknown, params?: GetBoardsParams): Error {
        const filterContext = this.getFilterContext(params);
    
        if (error instanceof JiraNotFoundError) {
          return new Error(
            `❌ **No Boards Found**\n\nNo boards found${filterContext}.\n\n**Solutions:**\n- Check your search criteria are correct\n- Try removing filters to see all boards\n- Verify you have permission to view boards\n\n**Example:** \`jira_get_boards type="scrum"\``,
          );
        }
    
        if (error instanceof JiraPermissionError) {
          return new Error(
            `❌ **Permission Denied**\n\nYou don't have permission to view boards${filterContext}.\n\n**Solutions:**\n- Check your JIRA permissions\n- Contact your JIRA administrator\n- Verify you're logged in with the correct account\n\n**Required Permissions:** Browse Projects`,
          );
        }
    
        if (error instanceof JiraApiError) {
          return new Error(
            `❌ **JIRA API Error**\n\n${error.message}\n\n**Solutions:**\n- Check your filter parameters are valid\n- Try removing filters to see all boards\n- Verify your project key is correct\n- Check board type is valid (scrum, kanban, simple)\n\n**Example:** \`jira_get_boards projectKeyOrId="PROJ" type="scrum"\``,
          );
        }
    
        if (error instanceof Error) {
          return new Error(
            `❌ **Board Retrieval Failed**\n\n${error.message}${filterContext}\n\n**Solutions:**\n- Check your parameters are valid\n- Try a simpler query first\n- Verify your JIRA connection\n\n**Example:** \`jira_get_boards maxResults=10\``,
          );
        }
    
        return new Error(
          `❌ **Unknown Error**\n\nAn unknown error occurred during board retrieval${filterContext}.\n\nPlease check your parameters and try again.`,
        );
      }
    
      /**
       * Get filter context for error messages
       */
      private getFilterContext(params?: GetBoardsParams): string {
        if (!params) return "";
    
        const filters = [];
        if (params.type) filters.push(`type: ${params.type}`);
        if (params.projectKeyOrId)
          filters.push(`project: ${params.projectKeyOrId}`);
        if (params.name) filters.push(`name: "${params.name}"`);
    
        return filters.length > 0 ? ` with filters (${filters.join(", ")})` : "";
      }
    }
  • Zod schema defining the input parameters for the jira_get_boards tool, including pagination, filtering by type/project/name, and other options.
    export const getBoardsParamsSchema = z.object({
      // Pagination
      startAt: z.number().int().min(0).optional().default(0),
      maxResults: z.number().int().min(1).max(50).optional().default(50),
    
      // Filtering options
      type: z.enum(["scrum", "kanban", "simple"]).optional(),
      name: z.string().min(1).optional(),
      projectKeyOrId: z.string().min(1).optional(),
    
      // Location filtering
      accountIdLocation: z.string().min(1).optional(),
      projectLocation: z.string().min(1).optional(),
      includePrivate: z.boolean().optional(),
      negateLocationFiltering: z.boolean().optional(),
    
      // Ordering and expansion
      orderBy: z.enum(["name", "type"]).optional(),
      expand: z.enum(["admins", "permissions"]).optional(),
    
      // Filter by saved filter
      filterId: z.string().min(1).optional(),
    });
  • Tool configuration defining the name, description, schema, and handler for jira_get_boards.
      {
        name: "jira_get_boards",
        description: "Get all accessible JIRA boards with filtering by type, project, and name",
        params: getBoardsParamsSchema.shape,
        handler: tools.jira_get_boards.handle.bind(tools.jira_get_boards),
      },
    ];
  • Factory creating the jira_get_boards tool handler wrapper that delegates to GetBoardsHandler instance.
    return {
      jira_get_boards: {
        handle: async (args: unknown) => getBoardsHandler.handle(args),
      },
    };
  • Tool registry configuration group that includes the board tools config for MCP server registration.
      groupName: "boards",
      configs: createBoardToolsConfig({
        jira_get_boards: tools.jira_get_boards,
      }),
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves data ('Get'), implying a read-only operation, but lacks details on permissions, rate limits, pagination (implied by parameters like 'startAt' and 'maxResults'), or error handling, which are critical for a tool with 12 parameters.

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, efficient sentence that front-loads the core purpose and key filtering options without unnecessary words. Every part earns its place, making it easy 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 high complexity (12 parameters, no annotations, no output schema), the description is incomplete. It lacks behavioral context, detailed parameter guidance, and output information, making it inadequate for an agent to use the tool effectively without additional inference or trial-and-error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions filtering by 'type, project, and name', which covers only 3 of the 12 parameters, leaving others like 'startAt', 'maxResults', 'expand', and 'filterId' unexplained. This partial coverage is insufficient for such a complex parameter set.

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 tool's purpose with a specific verb ('Get') and resource ('all accessible JIRA boards'), and mentions filtering capabilities. It distinguishes itself from siblings like 'jira_get_projects' or 'jira_get_sprints' by focusing on boards, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives. The description mentions filtering but doesn't specify scenarios, prerequisites, or exclusions, leaving the agent to infer usage from the tool name and context 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/Dsazz/mcp-jira'

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