Skip to main content
Glama

jira_get_sprint_issues

Retrieve all issues assigned to a specific sprint by sprint ID, with optional JQL filtering, to see planned or in-progress work.

Instructions

Get all issues assigned to a specific sprint. Use this to see what work is planned or in progress for a sprint. Get sprint IDs from jira_get_sprints. Can add JQL filter for additional narrowing.

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": {
      "sprintId": "<sprintId>"
    },
    "name": "jira_get_sprint_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
jqlNoAdditional JQL filter (e.g. status = "In Progress", assignee = currentUser())
startAtNoStarting index for pagination
sprintIdYesSprint ID (get from jira_get_sprints)
maxResultsNoMaximum number of results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.6/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 disclosure burden. It correctly scopes results to a single sprint and notes optional JQL narrowing, but says nothing about pagination behavior, result caps (maxResults default 50, max 100), permissions, or what happens with an invalid or closed sprint ID.

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?

Three short sentences with the core action front-loaded and no wasted preamble. The second sentence partially restates the first's intent, a minor redundancy but not damaging.

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 read-only list tool with fully described schema parameters and no output schema, the description covers purpose, usage context, and the prerequisite for obtaining a sprint ID. The main gap is the unmentioned pagination behavior, which matters since two of four parameters control it.

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 all four parameters including jql, startAt, and maxResults are already documented in the schema. The description only adds that JQL is for 'additional narrowing', which is mildly useful framing but no new syntax or constraint detail.

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 uses a specific verb and resource — 'Get all issues assigned to a specific sprint' — so the agent knows exactly what is returned. It does not explicitly contrast with look-alike siblings such as jira_get_board_issues, so differentiation is only implied by the sprint scoping.

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?

It states the intended use ('see what work is planned or in progress for a sprint') and a prerequisite workflow ('Get sprint IDs from jira_get_sprints'). It stops short of naming when-not-to-use it or which sibling to pick for board- or project-level issue retrieval.

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