Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

update_sprint

Update a Jira sprint's name, dates, goal, or state. Modify only specified fields; closed sprints accept only name and goal changes.

Instructions

Update sprint information (name, dates, goal, state). Only provided fields will be updated. For closed sprints, only name and goal can be updated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYesID of the sprint to update.
nameNoNew name for the sprint.
startDateNoNew start date (ISO 8601 format).
endDateNoNew end date (ISO 8601 format).
goalNoNew goal or objective for the sprint.
stateNoNew state: "future" for upcoming, "active" to start, "closed" to complete.

Implementation Reference

  • The tool handler for 'update_sprint' in the switch statement. Validates args using updateSprintSchema, calls jiraClient.updateSprint(), and returns a success message.
    case 'update_sprint': {
      const validatedArgs = await updateSprintSchema.validate(args);
      const _result = await jiraClient.updateSprint(validatedArgs);
    
      return {
        content: [
          {
            type: 'text',
            text: `Sprint ${validatedArgs.sprintId} updated successfully`,
          },
        ],
      };
    }
  • The JiraClient method that executes the actual Jira API call. Builds a PartiallyUpdateSprint payload with only the provided fields, then calls agileClient.sprint.partiallyUpdateSprint().
    async updateSprint(input: UpdateSprintInput) {
      try {
        const updateData: PartiallyUpdateSprint = { sprintId: input.sprintId };
    
        // Only include fields that are provided
        if (input.name !== undefined) updateData.name = input.name;
        if (input.startDate !== undefined) updateData.startDate = input.startDate;
        if (input.endDate !== undefined) updateData.endDate = input.endDate;
        if (input.goal !== undefined) updateData.goal = input.goal;
        if (input.state !== undefined) updateData.state = input.state;
    
        const response = await this.agileClient.sprint.partiallyUpdateSprint(updateData);
        return response;
      } catch (error) {
        throw new Error(`Failed to update sprint: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Yup validation schema for update_sprint input. Requires sprintId, and optionally accepts name, startDate, endDate, goal, and state.
    export const updateSprintSchema = yup.object({
      sprintId: yup.number().required('Sprint ID is required'),
      name: yup.string().optional(),
      startDate: yup.string().optional(),
      endDate: yup.string().optional(),
      goal: yup.string().optional(),
      state: yup.string().oneOf(['future', 'active', 'closed']).optional(),
    });
  • TypeScript type derived from the updateSprintSchema, used as input type for JiraClient.updateSprint().
    export type UpdateSprintInput = yup.InferType<typeof updateSprintSchema>;
  • MCP tool registration for 'update_sprint' in the createSprintTools function, defining its description and input JSON schema.
    {
      name: 'update_sprint',
      description: 'Update sprint information (name, dates, goal, state). Only provided fields will be updated. For closed sprints, only name and goal can be updated.',
      inputSchema: {
        type: 'object',
        properties: {
          sprintId: {
            type: 'number',
            description: 'ID of the sprint to update.',
          },
          name: {
            type: 'string',
            description: 'New name for the sprint.',
          },
          startDate: {
            type: 'string',
            description: 'New start date (ISO 8601 format).',
          },
          endDate: {
            type: 'string',
            description: 'New end date (ISO 8601 format).',
          },
          goal: {
            type: 'string',
            description: 'New goal or objective for the sprint.',
          },
          state: {
            type: 'string',
            enum: ['future', 'active', 'closed'],
            description: 'New state: "future" for upcoming, "active" to start, "closed" to complete.',
          },
        },
        required: ['sprintId'],
      },
    },
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses partial update behavior and closed-sprint restrictions. However, it omits return value, auth requirements, or side effects. The disclosed traits are valuable and not contradicted.

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: first lists fields, second adds constraints. No fluff. Front-loaded with action and immediately clear. Every sentence earns its place.

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 6-param mutable tool with no output schema or annotations, the description covers key behavioral aspects (partial update, closed-sprint limits). It lacks return value or error info but is fairly complete for its complexity. Could be slightly more detailed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage, so individual parameters are well-described. The description adds meta-information: only provided fields are updated, and constraints for closed sprints. This goes beyond individual schema descriptions.

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 'Update sprint information' with specific fields (name, dates, goal, state), distinguishing it from sibling tools like create_sprint, delete_sprint, and close_sprint. The verb 'update' and resource 'sprint' are precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides constraints (only provided fields updated; closed sprints limited) but does not explicitly guide when to use this tool versus alternatives like close_sprint or move_issue_to_sprint. The agent must infer from tool 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