Skip to main content
Glama
ParasSolanki

Jira MCP Server

by ParasSolanki

list_issues_from_sprint

Retrieve and display issues associated with a specific sprint in Jira by providing sprint and board IDs, with options to control result quantity and detail level.

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 main handler function that constructs the Jira API URL for fetching issues from a specific sprint on a board, makes the request, parses the response, and returns the issues.
    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);
    }
  • Zod input schema defining parameters for the list_issues_from_sprint tool: sprintId, boardId, optional 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.",
        ),
    });
  • Tool registration object defining the name, description, and input schema for the MCP tool.
    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"],
    };
  • src/app.ts:39-48 (registration)
    Array of all tools including LIST_ISSUES_FROM_SPRINT_TOOL, used by the MCP server for listing available tools.
    export const tools = [
      // list
      LIST_PROJECTS_TOOL,
      LIST_BOARDS_TOOL,
      LIST_SPRINTS_FROM_BOARD_TOOL,
      LIST_ISSUES_FROM_SPRINT_TOOL,
    
      // create
      CREATE_ISSUE_TOOL,
    ] satisfies Tool[];
  • Top-level handler dispatch for the tool: validates input, calls listIssuesFromSprint, handles errors, and formats response.
    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 provided, the description carries the full burden of behavioral disclosure. It only states the action ('List issues') without detailing permissions, rate limits, pagination behavior, or response format. This is insufficient for a tool with 5 parameters and no output schema, leaving critical behavioral traits unexplained.

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?

The description is a single, direct sentence with zero waste, efficiently conveying the core purpose without unnecessary elaboration. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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's complexity (5 parameters, no annotations, no output schema), the description is incomplete. It fails to address behavioral aspects like pagination, error handling, or return values, which are crucial for proper tool invocation. The minimal description doesn't compensate for the lack of structured data.

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 schema description coverage is 100%, so the input schema fully documents all 5 parameters. The description adds no additional meaning beyond what the schema provides, such as explaining relationships between parameters like 'sprintId' and 'boardId'. Baseline 3 is appropriate since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 resource ('issues from a sprint'), providing a basic understanding of the tool's function. However, it lacks specificity about scope or differentiation from sibling tools like 'list_boards' or 'list_sprints_from_board', making it somewhat vague but adequate.

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?

The description provides no guidance on when to use this tool versus alternatives, such as how it differs from other list tools or when it's appropriate for sprint-related queries. There's no mention of prerequisites, exclusions, or contextual usage, leaving the agent without direction.

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