Skip to main content
Glama

List Jira sprints

list_sprints
Read-only

Retrieve Jira board sprints by project key or board ID, filter by active, future, or closed state, and return sprint IDs, names, dates, and board details for issue assignment.

Instructions

List sprints of a Jira board, or of every board in a project, using the Agile API. Give project_key or board_id. state is a comma-separated filter of active, future, closed. Returns sprint id, name, state, startDate, endDate, boardId, and boardName. Use an id with move_issues_to_sprint.

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": "list_sprints"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoComma-separated sprint states: active, future, closed.active,future
board_idNoBoard ID. Takes precedence over project_key.
config_idNoJira instance to use, from list_configs. Omit for the default.
project_keyNoProject key, e.g. ONE. Lists sprints of all its boards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the return field list (id, name, state, startDate, endDate, boardId, boardName) and the default state filter behavior. It does not mention pagination, result caps, or what happens when both board_id and project_key are omitted, which is a notable gap for a 0-required-param tool.

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 scope, then invocation, then return shape, then the related tool. The state values are duplicated between description and schema, a minor redundancy, but nothing else is wasted.

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?

With four optional parameters and no output schema, the description covers the essentials: what gets listed, how to select a scope, the filter vocabulary, and the returned fields. Missing only edge behavior such as default behavior when neither scope parameter is supplied and any result limits.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description earns above that by supplying the cross-parameter rule that at least one of project_key or board_id should be provided and by restating the state filter as a comma-separated set of active/future/closed. Precedence of board_id over project_key is left to the schema, which already documents it.

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 sprints of a Jira board, or of every board in a project') and names the API surface (Agile API). The dual scoping (board vs. project) is stated up front, so the agent can distinguish this from siblings like move_issues_to_sprint without opening a 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?

Gives an explicit invocation rule ('Give project_key or board_id') that the schema alone would not convey, since every parameter is optional there. It also points forward to the consumer tool ('Use an id with move_issues_to_sprint'), but offers no when-not-to-use guidance or naming of alternative sprint-listing approaches.

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