Skip to main content
Glama
raalarcon9705

raalarcon-jira-mcp-server

delete_sprint

Delete a sprint and move all open issues to the backlog. Note: this action is irreversible.

Instructions

Delete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sprintIdYesID of the sprint to delete.

Implementation Reference

  • The main handler logic for the delete_sprint tool. Validates args using the schema, calls jiraClient.deleteSprint(), and returns a success message.
    case 'delete_sprint': {
      const validatedArgs = await deleteSprintSchema.validate(args);
      const _result = await jiraClient.deleteSprint(validatedArgs);
    
      return {
        content: [
          {
            type: 'text',
            text: `Sprint ${validatedArgs.sprintId} deleted successfully. All open issues moved to backlog.`,
          },
        ],
      };
    }
  • Registration of the delete_sprint tool with its name, description, and input schema.
    {
      name: 'delete_sprint',
      description: 'Delete a sprint. Once deleted, all open issues in the sprint will be moved to the backlog. This action is irreversible.',
      inputSchema: {
        type: 'object',
        properties: {
          sprintId: {
            type: 'number',
            description: 'ID of the sprint to delete.',
          },
        },
        required: ['sprintId'],
      },
    },
  • The JiraClient method that calls the Jira API (agileClient.sprint.deleteSprint) to actually delete the sprint.
    async deleteSprint(input: DeleteSprintInput) {
      try {
        const response = await this.agileClient.sprint.deleteSprint({
          sprintId: input.sprintId,
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to delete sprint: ${error instanceof Error ? error.message : 'Unknown error'}`);
      }
    }
  • Yup validation schema for delete_sprint: requires a sprintId (number).
    export const deleteSprintSchema = yup.object({
      sprintId: yup.number().required('Sprint ID is required'),
    });
  • src/index.ts:101-106 (registration)
    Routes delete_sprint requests to handleSprintTool in the main server handler.
      name.startsWith('delete_sprint') ||
      name.startsWith('create_sprint') ||
      name.startsWith('update_sprint') ||
      name.startsWith('close_sprint')
    ) {
      return await handleSprintTool(name, args || {}, this.jiraClient);
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the irreversible nature and that open issues move to backlog. However, it omits other behavioral details like auth requirements or effects on sprints with no issues.

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?

Three concise sentences: purpose, consequence, and irreversibility. Each sentence adds value with no redundancy or wasted words.

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 simple tool with one parameter and no output schema, the description covers the essential behavioral outcomes and constraints. Could mention prerequisites like sprint status but is largely complete.

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% for the single parameter, and the description adds no additional semantics beyond what the schema provides. Baseline score of 3 is appropriate.

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 'Delete a sprint' with a specific verb and resource. It distinguishes from sibling tools like close_sprint by detailing consequences (issues moved to backlog) and irreversibility.

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 explicit guidance on when to use this tool versus alternatives like close_sprint or update_sprint. The description implies permanent deletion but does not provide when-not-to-use or contrast with siblings.

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