Skip to main content
Glama

jira_update_sprint

Update an existing Jira sprint's name, goal, dates, or state to start, complete, or revert it; only specified fields change.

Instructions

Modify an existing sprint's name, goal, dates, or state. Change state to "active" to start a sprint, "closed" to complete it. Only fields you specify will be updated.

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>"
    },
    "name": "jira_update_sprint"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalNoNew sprint goal
nameNoNew sprint name
stateNoNew state: active (start sprint), closed (complete sprint), future (revert to planned)
endDateNoNew end date (ISO format)
sprintIdYesSprint ID to update (get from jira_get_sprints)
startDateNoNew start date (ISO format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It does make one valuable disclosure beyond structured data: 'Only fields you specify will be updated', which establishes partial-update semantics. It is silent on permission requirements, whether closing a sprint is reversible, and what happens to incomplete issues when a sprint is closed — real risks for a state-transition 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?

Three short sentences, front-loaded with the scope, then the state semantics, then the update contract. Every sentence earns its place and nothing is padded.

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?

Six parameters and no annotations or output schema, so the description needs to do heavy lifting. It covers the update contract but omits side effects of the closed/active transitions and any auth or permission expectations, leaving an agent without enough context to warn about irreversible sprint closure.

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% and the enum meanings for state are already spelled out in the schema, so the description's state explanation is largely redundant. The only added meaning is the partial-update contract, which is arguably behavioral rather than parameter-level. Baseline 3 applies.

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 (Modify) and resource (an existing sprint) plus the exact mutable surface: name, goal, dates, state. The word 'existing' distinguishes it from jira_create_sprint without the reader needing to open either schema.

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 sentence explaining that state=active starts a sprint and state=closed completes it is parameter guidance rather than tool-selection guidance. It gives no criteria for choosing this tool over jira_create_sprint or jira_move_issues_to_sprint, and no prerequisites are stated. Usage is implied by the verb rather than made explicit.

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