Skip to main content
Glama

Move Jira issues to sprint

move_issues_to_sprint

Move Jira issues into a sprint using a sprint ID and issue keys; handles batches of 50 and returns the moved issue keys.

Instructions

Move issues into a sprint (Agile API), in batches of 50. Get the sprint ID from list_sprints. Returns the sprint ID and the moved issue keys.

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": {
      "sprint_id": "<sprint_id>",
      "issue_keys": "<issue_keys>"
    },
    "name": "move_issues_to_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
config_idNoJira instance to use, from list_configs. Omit for the default.
sprint_idYesSprint ID from list_sprints.
issue_keysYesIssue keys to move, e.g. ["ONE-1", "ONE-2"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true). The description adds value beyond that with an operational constraint (batches of 50) and the return shape (sprint ID plus moved issue keys), which matters given idempotentHint=false. It does not say what happens on partial failure or for issues already in the sprint, leaving some behavioral gaps.

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 short sentences with zero waste: purpose and batching first, prerequisite pointer second, return value last. Every clause earns its place and nothing is buried.

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?

With 3 parameters, full schema coverage, and annotations present, the description covers purpose, prerequisite, batch limit, and return values; the absence of an output schema is partly offset by the stated return contents. Only failure/partial-success behavior for a non-idempotent mutation is left unaddressed.

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 sprint_id, issue_keys, and config_id are already fully documented, including the list_sprints and list_configs provenance. The description reinforces the sprint_id source and the batch bound on issue_keys but adds no new syntax or format meaning. Baseline 3 applies when the schema carries the load.

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 opens with a specific verb plus resource ("Move issues into a sprint") and adds scope detail ("Agile API") and a batching constraint. An agent can tell exactly what this does versus list_sprints, search_issues, or transition_issue without opening a schema.

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?

It states the prerequisite for the key input ("Get the sprint ID from list_sprints"), which tells the agent to call a sibling first. The 50-per-batch limit implicitly tells the agent to chunk large moves. There is no explicit when-not guidance or error/edge-case routing, but the context needed to invoke it is clear.

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