gitlab-mcp

List Group Iteration Cadences

gitlab_list_group_iteration_cadences

Read-onlyIdempotent

List a group's iteration cadences using GraphQL filters for active, automatic, title, duration, and ancestor groups; returns cadence global IDs.

Instructions

List a group's iteration cadences (GraphQL; no REST endpoint exists). Filters: active, automatic, title, duration_in_weeks, include_ancestor_groups. Returned IDs are cadence global IDs. Premium/Ultimate.

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": {
      "group_id": "<group_id>"
    },
    "name": "gitlab_list_group_iteration_cadences"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No
`active`	No
`group_id`	Yes
`automatic`	No
`duration_in_weeks`	No
`include_ancestor_groups`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real context beyond them: the surface is GraphQL-only with no REST equivalent, results are gated on Premium/Ultimate, and returned IDs are cadence global IDs rather than plain integers.

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?

Compact and front-loaded: purpose first, then filters, then return-value and tier caveats. The telegraphic filter list is efficient, though it occupies space without adding meaning beyond the schema.

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?

With no output schema, the note about global IDs is a useful partial substitute, and the GraphQL/tier caveats cover environment expectations. However, for a six-parameter list tool it omits pagination behavior, the shape of a cadence object, and any semantic explanation of the group_id anchor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description carries the full burden, yet it only enumerates filter property names (active, automatic, title, duration_in_weeks, include_ancestor_groups) without explaining their semantics. The required group_id is never mentioned, and nothing clarifies what include_ancestor_groups does or how duration_in_weeks is bounded.

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?

Uses a specific verb and resource ('List a group's iteration cadences') and disambiguates from the sibling gitlab_list_group_iterations by naming 'cadences' explicitly. It also adds distinguishing facts (GraphQL-only, Premium/Ultimate) that let an agent identify the tool without opening the 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 tier note ('Premium/Ultimate') and GraphQL note imply availability conditions, but there is no explicit when-to-use vs when-not-to-use guidance. It never names gitlab_list_group_iterations or the cadence create/update/delete siblings to route the agent among them, leaving the choice to inference.

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

Deploy Server