Skip to main content
Glama

jira_move_issues_to_sprint

Move one or more Jira issues into a specified sprint for sprint planning, removing them from any current sprint; use with jira_get_sprints to find the sprint ID.

Instructions

Add/move one or more issues into a sprint for sprint planning. Issues will be removed from their current sprint (if any) and added to the specified sprint. Get sprint ID from jira_get_sprints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sprintId": "<sprintId>",
      "issueKeys": "<issueKeys>"
    },
    "name": "jira_move_issues_to_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
sprintIdYesTarget sprint ID (get from jira_get_sprints)
issueKeysYesArray of issue keys to move (e.g., ["KP-1", "KP-2", "KP-3"])

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the crucial side effect: issues are removed from their current sprint before being added. It omits permissions, behavior on invalid or closed sprint targets, and what happens on partial failure across a multi-issue array.

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 short sentences, front-loaded with the action and the side effect, ending with the prerequisite lookup. Nothing is redundant or padded.

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 two-parameter mutation with no output schema, the description covers the action, the destructive-adjacent effect, and the prerequisite. It could go further on target-sprint constraints and whether the response lists moved issues.

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 description coverage is 100%, so both parameters are already documented, including the example issue-key format. The description's pointer to jira_get_sprints for the sprint ID duplicates the schema text rather than adding new semantics.

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?

States a specific verb and resource ('Add/move one or more issues into a sprint') plus the planning context, which clearly separates it from read-side siblings like jira_get_sprints or jira_get_sprint_issues and from jira_create_sprint.

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?

Frames the tool as a sprint-planning action and explicitly routes the agent to jira_get_sprints for the sprint ID. It stops short of stating exclusions, such as whether issues may be moved into a closed sprint or what to do instead for backlog placement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.