Skip to main content
Glama

list_group_iterations

Retrieve and filter GitLab group iterations by state, search terms, or timeframe to manage project timelines and track progress.

Instructions

List group iterations with filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idNoGroup ID or URL-encoded path
stateNoReturn opened, upcoming, current, closed, or all iterations.
searchNoReturn only iterations with a title matching the provided string.
search_inNoFields in which fuzzy search should be performed with the query given in the argument search. The available options are title and cadence_title. Default is [title].
include_ancestorsNoInclude iterations for group and its ancestors. Defaults to true.
include_descendantsNoInclude iterations for group and its descendants. Defaults to false.
updated_beforeNoReturn only iterations updated before the given datetime. Expected in ISO 8601 format (2019-03-15T08:00:00Z).
updated_afterNoReturn only iterations updated after the given datetime. Expected in ISO 8601 format (2019-03-15T08:00:00Z).
pageNoPage number for pagination (default: 1)
per_pageNoNumber of items per page (max: 100, default: 20)

Implementation Reference

  • Input schema (parameters) for the 'list_group_iterations' tool, defining validation for group_id and optional filters like state, search, pagination matching GitLab Groups Iterations API.
    export const ListGroupIterationsSchema = z
      .object({
        group_id: z.coerce.string().describe("Group ID or URL-encoded path"),
        state: z
          .enum(["opened", "upcoming", "current", "closed", "all"])
          .optional()
          .describe("Return opened, upcoming, current, closed, or all iterations."),
        search: z
          .string()
          .optional()
          .describe("Return only iterations with a title matching the provided string."),
        search_in: z
          .array(z.enum(["title", "cadence_title"]))
          .optional()
          .describe(
            "Fields in which fuzzy search should be performed with the query given in the argument search. The available options are title and cadence_title. Default is [title]."
          ),
        include_ancestors: z.boolean()
          .optional()
          .describe("Include iterations for group and its ancestors. Defaults to true."),
        include_descendants: z.boolean()
          .optional()
          .describe("Include iterations for group and its descendants. Defaults to false."),
        updated_before: z
          .string()
          .optional()
          .describe(
            "Return only iterations updated before the given datetime. Expected in ISO 8601 format (2019-03-15T08:00:00Z)."
          ),
        updated_after: z
          .string()
          .optional()
          .describe(
            "Return only iterations updated after the given datetime. Expected in ISO 8601 format (2019-03-15T08:00:00Z)."
          ),
      })
      .merge(PaginationOptionsSchema);
  • Output schema defining the structure of a GitLab Group Iteration object returned by the 'list_group_iterations' tool.
    export const GroupIteration = z.object({
      id: z.coerce.string(),
      iid: z.coerce.string(),
      sequence: z.number(),
      group_id: z.coerce.string(),
      title: z.string().optional().nullable(),
      description: z.string().optional().nullable(),
      state: z.number(),
      created_at: z.string(),
      updated_at: z.string(),
      due_date: z.string().optional().nullable(),
      start_date: z.string().optional().nullable(),
      web_url: z.string().optional().nullable(),
    });
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it's a listing operation with filtering. It doesn't disclose behavioral traits like pagination behavior (implied by parameters but not described), rate limits, authentication requirements, or what happens when no iterations match filters.

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, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized and front-loaded with the essential information.

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 read-only listing tool with 10 well-documented parameters but no output schema or annotations, the description is minimally adequate. It identifies the resource but doesn't explain return format, error conditions, or relationship to sibling tools, leaving gaps in contextual understanding.

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 fully documents all 10 parameters. The description adds no additional parameter semantics beyond mentioning 'filtering options', which is already covered by the detailed schema descriptions. Baseline 3 is appropriate when schema does all the work.

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?

The description clearly states the verb ('List') and resource ('group iterations'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_issues' or 'list_merge_requests' beyond mentioning 'group iterations' specifically.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'list_issues' or 'list_projects'. It mentions 'filtering options' but doesn't specify scenarios where filtering by iteration state or search would be appropriate.

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

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