gitlab-mcp

Create Group Iteration

gitlab_create_group_iteration

Creates a GitLab group iteration with a manual cadence ID and optional title, description, start date, and due date in YYYY-MM-DD format.

Instructions

Create an iteration in a group. Recent GitLab versions require iterations_cadence_id of a manual (non-automatic) cadence. Dates use YYYY-MM-DD. 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_create_group_iteration"
  }
}

Input Schema

Name	Required	Description	Default
`title`	No
`due_date`	No
`group_id`	Yes
`start_date`	No
`description`	No
`iterations_cadence_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare this is a non-destructive, non-idempotent, open-world write. The description adds two genuinely non-derivable facts: tier availability and the version-dependent manual-cadence constraint. It omits required permissions/role, what happens on duplicate titles or overlapping dates, and there is no output schema, so the return value is unexplained.

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?

Three short sentences, front-loaded with the action and followed by the two constraints that most affect success. The 'Premium/Ultimate.' sentence fragment is telegraphic but readable and earns its place by flagging tier gating.

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?

For a 6-parameter mutation tool with no output schema and 0% schema coverage, the description covers the highest-risk constraint (cadence type) and tier but leaves permissions, duplicate/overlap behavior, and return shape unspecified. Adequate minimum, not complete.

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 0% across 6 parameters, so the description must compensate. It clarifies the date format (redundant with the regex pattern) and adds real meaning for iterations_cadence_id by requiring a manual cadence, but title, description, and group_id semantics go unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create an iteration in a group'), which is enough for an agent to distinguish it from sibling cadence tools like gitlab_create_group_iteration_cadence or gitlab_update_group_iteration. It stops short of explicitly differentiating from those siblings by name.

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?

Includes useful gating context ('Recent GitLab versions require iterations_cadence_id of a manual (non-automatic) cadence' and 'Premium/Ultimate'), which tells the agent when the call will fail. It never states when to choose this over creating a cadence first or over update_group_iteration, so routing remains implicit.

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

Deploy Server