Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

get_sprint_issues

Retrieve all issues assigned to a specific sprint to view current tickets. Specify sprint ID and optional result limit.

Instructions

Get all issues in a specific sprint. Useful for viewing what tickets are currently in a sprint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYesThe ID of the sprint to get issues from. Use get_sprints to find available sprint IDs.
maxResultsNoMaximum number of issues to return (1-100). Defaults to 50.

Implementation Reference

  • Handler function for get_sprint_issues tool. Validates args using getSprintIssuesSchema, calls jiraClient.getSprintIssues(), then maps the response to essential fields (key, summary, status, assignee, priority) and returns them as JSON.
    case 'get_sprint_issues': {
      const validatedArgs = await getSprintIssuesSchema.validate(args);
      const issues = await jiraClient.getSprintIssues(validatedArgs);
    
      // Extract only essential fields to reduce token usage
      const essentialIssues = issues.issues?.map((issue) => ({
        key: issue.key,
        summary: issue.fields?.summary || 'No summary',
        status: issue.fields?.status?.name || 'Unknown',
        assignee: issue.fields?.assignee?.displayName || 'Unassigned',
        priority: issue.fields?.priority?.name || 'None'
      })) || [];
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(essentialIssues, null, 2),
          },
        ],
      };
    }
  • JiraClient method that makes the actual API call using the Jira Agile client's getIssuesForSprint() with sprintId and maxResults parameters, returning the issues response.
    async getSprintIssues(input: GetSprintIssuesInput) {
      try {
        const response = await this.agileClient.sprint.getIssuesForSprint({
          sprintId: input.sprintId,
          maxResults: input.maxResults,
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to get sprint issues: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Yup validation schema for get_sprint_issues tool. Defines sprintId (required number) and maxResults (number 1-100, default 50).
    export const getSprintIssuesSchema = yup.object({
      sprintId: yup.number().required('Sprint ID is required'),
      maxResults: yup.number().min(1).max(100).default(50),
    });
  • Tool registration definition for get_sprint_issues. Defines the tool name, description, and JSON Schema input format for the MCP protocol.
      name: 'get_sprint_issues',
      description: 'Get all issues in a specific sprint. Useful for viewing what tickets are currently in a sprint.',
      inputSchema: {
        type: 'object',
        properties: {
          sprintId: {
            type: 'number',
            description: 'The ID of the sprint to get issues from. Use get_sprints to find available sprint IDs.',
          },
          maxResults: {
            type: 'number',
            description: 'Maximum number of issues to return (1-100). Defaults to 50.',
            default: 50,
          },
        },
        required: ['sprintId'],
      },
    },
  • src/index.ts:99-106 (registration)
    Routes get_sprint_issues calls to handleSprintTool in the MCP server's CallToolRequestSchema handler.
      name.startsWith('get_sprint_issues') ||
      name.startsWith('get_agile_boards') ||
      name.startsWith('delete_sprint') ||
      name.startsWith('create_sprint') ||
      name.startsWith('update_sprint') ||
      name.startsWith('close_sprint')
    ) {
      return await handleSprintTool(name, args || {}, this.jiraClient);
Behavior2/5

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

The description claims 'Get all issues' but the schema includes a maxResults parameter with a default of 50, implying pagination. This contradiction is not disclosed, and no other behavioral traits are mentioned.

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 two sentences, front-loaded with the core purpose, and contains no unnecessary words.

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 that there is no output schema, the description should provide some indication of the response structure or fields. It does not, and also omits mention of the maxResults limit that affects the result set.

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 coverage is 100%, and the description adds no new parameter-specific information beyond what the schema already provides.

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?

The description clearly states 'Get all issues in a specific sprint' with a specific verb and resource, and distinguishes it from sibling tools like close_sprint or get_sprints.

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?

The description says 'Useful for viewing what tickets are currently in a sprint,' providing clear context for when to use the tool. It does not explicitly mention alternatives, but the purpose is straightforward.

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/raalarcon9705/jira-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server