Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_issues_from_sprint

Retrieve all issues assigned to a specific sprint on a Jira board. Uses board and sprint IDs to return tasks, bugs, and stories.

Instructions

List issues from a sprint

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYesThe ID of the sprint
boardIdYesThe ID of the board
maxResultsNoThe maximum number of results to return, (default: 5, max: 100)
startAtNoThe starting index of the returned boards
expandNoUse this parameter to include additional information in the response. This parameter accepts a comma-separated list. Expand options include: `schema` and `names`. Comma separated list of options.

Implementation Reference

  • The handler function that executes the 'list_issues_from_sprint' tool logic. It constructs a Jira Agile API URL, fetches issues from a sprint, validates the response, and returns the result.
    export async function listIssuesFromSprint(input: ListIssuesFromSprintInput) {
      const url = new URL(
        `/rest/agile/1.0/board/${input.boardId}/sprint/${input.sprintId}/issue`,
        env.JIRA_BASE_URL,
      );
    
      if (input.expand) url.searchParams.set("expand", input.expand);
      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);
    
      const result = listIssuesFromSprintSchema.safeParse(json.value);
    
      if (!result.success) {
        return err(new Error("Invalid response from Jira"));
      }
    
      return ok(result.data);
    }
  • Input schema for the tool, defining sprintId (required), boardId (required), and optional parameters maxResults, startAt, expand.
    export const listIssuesFromSprintInputSchema = z.object({
      sprintId: z.string().describe("The ID of the sprint"),
      boardId: z.string().describe("The ID of the board"),
      maxResults: z
        .number()
        .optional()
        .describe(
          "The maximum number of results to return, (default: 5, max: 100)",
        ),
      startAt: z
        .number()
        .optional()
        .describe("The starting index of the returned boards"),
      expand: z
        .string()
        .optional()
        .describe(
          "Use this parameter to include additional information in the response. This parameter accepts a comma-separated list. Expand options include: `schema` and `names`. Comma separated list of options.",
        ),
    });
  • Response schema for parsing the Jira API response, containing pagination fields and an array of issues conforming to issueSchema.
    const listIssuesFromSprintSchema = z.object({
      maxResults: z.number().optional(),
      startAt: z.number().optional(),
      expand: z.string().optional(),
      total: z.number().optional(),
      issues: z.array(issueSchema),
    });
  • Tool definition object for registration, with name 'list_issues_from_sprint', description, and JSON Schema input.
    export const LIST_ISSUES_FROM_SPRINT_TOOL: Tool = {
      name: "list_issues_from_sprint",
      description: "List issues from a sprint",
      inputSchema: zodToJsonSchema(
        listIssuesFromSprintInputSchema,
      ) as Tool["inputSchema"],
    };
    
    export type ListIssuesFromSprintInput = z.output<
  • src/app.ts:61-85 (registration)
    Registration in the MCP server's CallToolRequestSchema handler: routes the 'list_issues_from_sprint' tool call to validation and execution.
    if (name === LIST_ISSUES_FROM_SPRINT_TOOL.name) {
      const input = listIssuesFromSprintInputSchema.safeParse(args);
    
      if (!input.success) {
        return {
          isError: true,
          content: [{ type: "text", text: "Invalid input" }],
        };
      }
    
      const result = await listIssuesFromSprint(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?

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic action, omitting details like pagination (implied by maxResults/startAt), default results, error behavior, or authentication requirements. This is insufficient for an agent to understand the tool's full behavior.

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?

The description is extremely concise (4 words) with no wasted text. However, it borders on under-specification, as it could benefit from a brief qualifier (e.g., 'paginated list'). Nonetheless, it is efficient for a simple tool.

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?

Given the tool has 5 parameters (2 required) and no output schema, the description is too minimal. It fails to explain return structure, parameter expected formats (e.g., sprintId format), or how results are ordered. An agent would struggle to use this tool correctly without additional context.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema already provides meaning. The description adds no additional parameter-level context beyond the schema. Baseline score of 3 is appropriate.

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 'List issues from a sprint' clearly states the verb (list) and the resource (issues from a sprint), distinguishing it from sibling tools like list_boards or list_sprints_from_board. However, it lacks specificity on scope or filtering options that would enhance clarity.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., search issues, list all issues), nor does it specify prerequisites like the need for valid sprintId and boardId.

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