Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get team iterations

get_team_iterations

Retrieves Targetprocess team iterations (sprints), optionally filtered by team, so you can resolve a sprint name to its ID before creating or updating user stories and bugs.

Instructions

Get Targetprocess team iterations (sprints), optionally filtered by team. Use this to resolve a sprint/iteration name to an ID before calling create_user_story, create_bug, update_user_story, or update_bug with teamIterationId. CRITICAL WORKFLOW: IF the user specified a team by name (not ID), call "get_teams" first to find the matching team and use its ID as teamId.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_team_iterations"
  }
}

Input Schema

NameRequiredDescriptionDefault
teamIdNoOptional Team ID to filter iterations by — resolve it via "get_teams" first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the key behavioral trait: this is a lookup that produces an ID consumed by other tools, and it must be sequenced after get_teams when only a team name is known. It does not cover pagination, result ordering, or what happens when teamId is invalid or unknown, which leaves a modest gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and the workflow caveat follows; overall it is short and every sentence earns its place. The all-caps 'CRITICAL WORKFLOW' heading is slightly heavy for a single-optional-parameter read tool.

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 one-optional-parameter read with no output schema, the description covers what it returns conceptually (iterations/sprints with IDs) and the prerequisite chain. Only the shape of returned iteration data and failure behavior are unstated, which an agent could reasonably infer.

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% and the schema already says teamId is an optional team filter resolved via get_teams, so the description largely restates it. The 'IF the user specified a team by name (not ID)' framing adds a little operational meaning but no new detail on format or behavior.

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 ('Get Targetprocess team iterations (sprints)') plus scope ('optionally filtered by team'), which cleanly separates it from get_teams and the other get_* lookups in the sibling list.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use: resolve a sprint/iteration name to an ID before calling create_user_story, create_bug, update_user_story, or update_bug. It also names the prerequisite alternative for the team-name case (call get_teams first), which is exactly the routing an agent needs.

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

Deploy Server

Other Tools