Skip to main content
Glama

jira_get_board_issues

Retrieve all issues from a Jira Agile board's backlog and active sprints, with optional JQL filtering and pagination to locate relevant work items.

Instructions

Get all issues visible on a specific Jira Agile board. Returns issues in the board's backlog and active sprints. Can combine with JQL for additional filtering. Use jira_get_boards first to find the board ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "boardId": "<boardId>"
    },
    "name": "jira_get_board_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlNoAdditional JQL filter to narrow results (e.g., "assignee = currentUser()")
boardIdYesBoard ID (get from jira_get_boards)
startAtNoStarting index for pagination
maxResultsNoMaximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral load. It does disclose the result scope (backlog and active sprints) and that JQL filtering is additive, but says nothing about pagination behavior, result totals, or permission requirements for the board. That is meaningful but partial coverage for a read tool with zero annotation support.

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?

Three short sentences with zero redundancy, front-loaded with the core action and scope before the optional filtering note and the prerequisite. Every sentence carries actionable information.

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?

With no output schema and no annotations, the description is the only place to learn what comes back, and it only says "returns issues" without indicating shape, count semantics, or pagination signaling. For a list tool capped at 100 results per call, that is a real gap an agent would want filled. Adding the prerequisite and JQL notes partially compensates.

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 boardId, jql, startAt, and maxResults are already documented with defaults, bounds, and an example. The description reinforces the boardId provenance (jira_get_boards) and the additive nature of JQL but adds no syntax or constraint detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("Get all issues visible on a specific Jira Agile board") and scopes the result set to backlog plus active sprints, which distinguishes it in substance from a sprint-only fetch. It stops short of naming jira_get_sprint_issues as the alternative, so the distinction must be inferred from the scope sentence rather than being explicit.

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?

Gives a concrete prerequisite workflow: "Use jira_get_boards first to find the board ID," which is exactly the routing an agent needs. It also explains the JQL combination as an optional refinement. It does not state when NOT to use this tool (e.g., when the sprint is already known), so it falls short of full alternatives coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.