Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_boards

Retrieve boards for a Jira project. Filter by name, type, and paginate results to find the boards you need.

Instructions

List boards from a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectKeyOrIdYesThe key or ID of the project
nameNoThe name of the boards to return, Must be less than 255 characters.
maxResultsNoThe maximum number of results to return, (max: 100)
startAtNoThe starting index of the returned boards
typeNoThe type of boards to return

Implementation Reference

  • The main handler function that executes the 'list_boards' tool logic. It constructs a Jira Agile REST API URL with query parameters (projectKeyOrId, name, type, startAt, maxResults), calls $jiraJson to fetch boards, and returns the JSON result or an error.
    export async function listBoards(input: ListBoardsInput) {
      const url = new URL(`/rest/agile/1.0/board`, env.JIRA_BASE_URL);
    
      url.searchParams.set("projectKeyOrId", input.projectKeyOrId);
    
      if (input.name) url.searchParams.set("name", input.name);
    
      if (input.type) url.searchParams.set("type", input.type);
    
      if (input.startAt) url.searchParams.set("startAt", input.startAt.toString());
    
      if (input.maxResults)
        url.searchParams.set("maxResults", input.maxResults.toString());
    
      const json = await $jiraJson(url.toString());
    
      if (json.isErr()) return err(json.error);
    
      return ok(json.value);
    }
  • Zod schema for validating the 'list_boards' tool input. Defines fields: projectKeyOrId (required string), name (optional string), maxResults (optional number), startAt (optional number), type (optional enum 'scrum'|'kanban').
    export const listBoardsInputSchema = z.object({
      projectKeyOrId: z.string().describe("The key or ID of the project"),
      name: z
        .string()
        .optional()
        .describe(
          "The name of the boards to return, Must be less than 255 characters.",
        ),
      maxResults: z
        .number()
        .optional()
        .describe("The maximum number of results to return, (max: 100)"),
      startAt: z
        .number()
        .optional()
        .describe("The starting index of the returned boards"),
      type: z
        .enum(["scrum", "kanban"])
        .optional()
        .describe("The type of boards to return"),
    });
  • Tool definition object LIST_BOARDS_TOOL with name 'list_boards', description 'List boards from a project', and the input schema converted to JSON Schema.
    export const LIST_BOARDS_TOOL: Tool = {
      name: "list_boards",
      description: "List boards from a project",
      inputSchema: zodToJsonSchema(listBoardsInputSchema) as Tool["inputSchema"],
    };
  • src/app.ts:39-48 (registration)
    Registration of LIST_BOARDS_TOOL in the tools array that gets returned via ListToolsRequestSchema handler.
    export const tools = [
      // list
      LIST_PROJECTS_TOOL,
      LIST_BOARDS_TOOL,
      LIST_SPRINTS_FROM_BOARD_TOOL,
      LIST_ISSUES_FROM_SPRINT_TOOL,
    
      // create
      CREATE_ISSUE_TOOL,
    ] satisfies Tool[];
  • CallToolRequestSchema handler that routes 'list_boards' calls: parses input, calls listBoards(), and returns the JSON result or an error.
    if (name === LIST_BOARDS_TOOL.name) {
      const input = listBoardsInputSchema.safeParse(args);
    
      if (!input.success) {
        return {
          isError: true,
          content: [{ type: "text", text: "Invalid input" }],
        };
      }
    
      const result = await listBoards(input.data);
    
      if (result.isErr()) {
        console.error(result.error.message);
        return {
          isError: true,
          content: [{ type: "text", text: "An error occurred" }],
        };
      }
    
      return {
        content: [
          { type: "text", text: JSON.stringify(result.value, null, 2) },
        ],
      };
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose read-only nature, pagination behavior, or error handling. Only implies listing without side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, 4 words, no wasted text. However, it could be expanded without losing conciseness.

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?

Description lacks return value info, pagination details, and filtering logic. With 5 parameters and no output schema, it is underspecified.

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 descriptions cover all 5 parameters with 100% coverage, so description adds no extra meaning beyond the schema. Baseline score of 3.

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?

Description clearly states the tool lists boards from a project, with a specific verb and resource. It is distinct from sibling tools (list_projects, list_sprints_from_board) but does not explicitly differentiate 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 on when to use this tool versus alternatives. The description does not mention context or prerequisites.

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

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