@wanadev/mcp-gitlab

list_epics

Read-only

List GitLab epics from a specified group. Filter by state, text search, or labels.

Instructions

Lister les epics d'un groupe GitLab. Filtrer par etat, recherche textuelle ou labels.

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": "list_epics"
  }
}

Input Schema

Name	Required	Description
`group_id`	Yes	ID ou chemin URL du groupe GitLab (ex: '42' ou 'wanadev/kp1'). Si vous n'avez que le nom, appelez d'abord list_groups pour trouver le chemin exact.
`state`	No	Filtrer par etat (defaut: all)
`search`	No	Recherche textuelle dans le titre/description
`labels`	No	Filtrer par labels (separes par virgule)
`order_by`	No	Trier par champ
`sort`	No	Ordre de tri

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.8.0Jun 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, indicating safe read operation. The description adds no further behavioral details such as pagination, limits, or side effects, so it minimally augments the annotation.

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 front-loads the core purpose. No wasted words.

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 description should explain what is returned (e.g., list of epics with fields). It lacks details on pagination, default limit, and output structure, leaving some uncertainty for the agent.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds value by explaining the group_id parameter with a hint to call list_groups first, which goes beyond the schema description.

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 the tool lists epics of a GitLab group with filtering options, which distinguishes it from sibling tools that operate on individual epics (e.g., get_epic, close_epic).

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 implies usage for listing epics with filters, but does not explicitly mention when not to use it or alternatives like get_epic for single epic retrieval. The context is clear enough for an AI agent.

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

Deploy Server