Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

Iterations

list_iterations
Read-onlyIdempotent

Retrieve iterations (sprints) for a GitLab group with cadence information. Supports filtering by state and pagination for complete results.

Instructions

List iterations (sprints) for a group with cadence info. Requires GitLab Premium/Ultimate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of iterations to retrieve
stateNoFilter by state: upcoming, current, opened, closed (omit for all)
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
groupPathYesFull path of the group (e.g., "my-group" or "parent/child-group")
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'with cadence info' but does not contradict annotations. It provides minimal additional behavioral context beyond what annotations convey.

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?

The description is a single sentence of 10 words, front-loading the purpose. Every word earns its place; no redundancy or filler.

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 no output schema, the description could hint at return fields, but it mentions 'cadence info'. The tool has 6 parameters (all documented) and annotations cover safety. Overall sufficient for a list tool, though a bit more detail on pagination or response structure would improve completeness.

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 the schema already documents all parameters thoroughly. The description adds no per-parameter details beyond 'cadence info', which is vague. Baseline 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 'List iterations (sprints) for a group with cadence info', which is a specific verb+resource. It distinguishes from sibling tools like list_milestones and list_work_items by explicitly mentioning 'iterations'.

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?

The description mentions the prerequisite 'Requires GitLab Premium/Ultimate', which helps the agent determine when the tool is available. However, it does not explicitly state when to use this tool versus alternatives, though the name and purpose make it clear.

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/ttpears/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server