Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

create_sprint

Create a sprint in Jira by providing a name and origin board ID; optionally include start date, end date, or goal.

Instructions

Create a new sprint. Sprint name and origin board ID are required. Start date, end date, and goal are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the sprint to create.
originBoardIdYesID of the board where the sprint will be created.
startDateNoStart date of the sprint (ISO 8601 format).
endDateNoEnd date of the sprint (ISO 8601 format).
goalNoGoal or objective of the sprint.

Implementation Reference

  • The handler function for the 'create_sprint' tool. Validates args using createSprintSchema, calls jiraClient.createSprint(), and returns essential sprint fields (id, name, state, goal).
    case 'create_sprint': {
      const validatedArgs = await createSprintSchema.validate(args);
      const result = await jiraClient.createSprint(validatedArgs);
    
      // Extract only essential fields
      const essentialSprint = {
        id: result.id,
        name: result.name,
        state: result.state,
        goal: result.goal
      };
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(essentialSprint, null, 2),
          },
        ],
      };
    }
  • Tool registration for 'create_sprint' in createSprintTools(). Defines name, description, and inputSchema with required fields (name, originBoardId) and optional fields (startDate, endDate, goal).
    {
      name: 'create_sprint',
      description: 'Create a new sprint. Sprint name and origin board ID are required. Start date, end date, and goal are optional.',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the sprint to create.',
          },
          originBoardId: {
            type: 'number',
            description: 'ID of the board where the sprint will be created.',
          },
          startDate: {
            type: 'string',
            description: 'Start date of the sprint (ISO 8601 format).',
          },
          endDate: {
            type: 'string',
            description: 'End date of the sprint (ISO 8601 format).',
          },
          goal: {
            type: 'string',
            description: 'Goal or objective of the sprint.',
          },
        },
        required: ['name', 'originBoardId'],
      },
    },
  • Yup validation schema for create_sprint. Requires 'name' and 'originBoardId', with optional 'startDate', 'endDate', and 'goal' strings.
    export const createSprintSchema = yup.object({
      name: yup.string().required('Sprint name is required'),
      originBoardId: yup.number().required('Origin board ID is required'),
      startDate: yup.string().optional(),
      endDate: yup.string().optional(),
      goal: yup.string().optional(),
    });
  • The JiraClient.createSprint() method that calls the underlying jira.js AgileClient.sprint.createSprint() API with name, originBoardId, startDate, endDate, and goal.
    async createSprint(input: CreateSprintInput) {
      try {
        const response = await this.agileClient.sprint.createSprint({
          name: input.name,
          originBoardId: input.originBoardId,
          startDate: input.startDate,
          endDate: input.endDate,
          goal: input.goal,
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to create sprint: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • src/index.ts:96-106 (registration)
    Tool routing in the main MCP server: routes 'create_sprint' (via name.startsWith('create_sprint')) to handleSprintTool.
    } else if (
      name.startsWith('get_sprints') ||
      name.startsWith('move_issue_to_sprint') ||
      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?

No annotations are provided, so the description must carry the full burden. It only describes parameters and does not disclose behavioral traits like side effects, authorization needs, or idempotency, which are critical for a mutation tool.

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?

Two sentences that are front-loaded with the purpose and immediately specify requirements. Every word is necessary; no fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not specify the return value or possible errors. While the tool is simple, the lack of output schema or result description leaves a gap for an agent to understand what to expect after creation.

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% with clear descriptions for each parameter. The description restates the required/optional distinction already captured by the 'required' array in the schema, but adds no additional semantic value.

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?

Description clearly states the action 'create a new sprint' and identifies the resource. It distinguishes from sibling tools like close_sprint, delete_sprint, and update_sprint by its specific verb and resource.

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 provides clear context on required vs optional parameters, implying when to use. However, it does not explicitly state when not to use or mention alternatives, but the tool's purpose is unambiguous given sibling names.

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