Skip to main content
Glama

jira_get_boards

List Jira Agile Scrum and Kanban boards to find board IDs for sprint or issue queries. Filter results by project key or board type for targeted board discovery.

Instructions

List all Jira Agile boards (Scrum and Kanban). Boards organize issues for agile teams. Use this to find board IDs needed for jira_get_sprints or jira_get_board_issues. Can filter by project or board type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jira_get_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by board type: scrum (has sprints) or kanban (continuous flow)
startAtNoStarting index for pagination
maxResultsNoMaximum number of results
projectKeyNoFilter boards by project key (e.g., KP)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. "List all" implies a non-mutating read and the filter sentence hints at scoping, but nothing is said about visibility/permissions, whether results are paginated or capped, rate limits, or the shape of returned records beyond board IDs. Adequate but with clear disclosure gaps.

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?

Four short sentences, front-loaded with the core action, then purpose, then the routing to downstream tools, then filtering. The only soft sentence is "Boards organize issues for agile teams," which is mild background but does frame the Scrum/Kanban distinction.

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?

For a zero-required-parameter read-only lister with no output schema, the definition covers what it returns (boards), why an agent wants it (board IDs), and how filters work. The main residual gap is that no output schema exists and the description doesn't sketch the response fields, but the tool's simplicity keeps this a minor omission.

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 baseline is 3; the schema already explains type, startAt, maxResults, and projectKey with examples. The description's "Can filter by project or board type" only echoes those fields and adds no syntax or behavior detail beyond them.

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?

States a specific verb and resource ("List all Jira Agile boards") and scopes it to Scrum and Kanban, so an agent knows exactly what it retrieves. It also anchors the tool against siblings by naming jira_get_sprints and jira_get_board_issues as downstream consumers, making it distinguishable without opening any schema.

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?

"Use this to find board IDs needed for jira_get_sprints or jira_get_board_issues" gives a concrete when-to-use rule plus the alternative tools. It stops short of stating when *not* to use it (e.g., if a board ID is already known) or any prerequisites, so it falls just shy of the top mark.

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