gitlab-mcp

List Group Members

gitlab_list_group_members

Read-onlyIdempotent

List direct members of a GitLab group to find reviewers or assignees by name; enable inheritance to include members from parent groups.

Instructions

List direct group members by default, for example to find reviewers or assignees by name; set include_inheritance=true to include members inherited from parent groups.

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_members"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`query`	No
`group_id`	Yes
`per_page`	No
`user_ids`	No
`skip_users`	No
`include_inheritance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds real behavioral context beyond that: results are limited to direct members unless inheritance is requested, which materially changes the result set. It says nothing about pagination behavior despite the presence of page/per_page parameters.

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?

A single sentence with no filler, and the most important fact (direct members by default) is front-loaded ahead of the inheritance override. Every clause carries information.

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?

It covers the default-vs-inherited distinction, which is the main way an agent could get this call subtly wrong, and there is no output schema requiring explanation. The gap is the undocumented filtering and pagination parameters, which leaves the definition short of complete for a 7-parameter tool.

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 7 parameters, so the description must carry the burden and it only explains include_inheritance. The filtering semantics of query, user_ids, skip_users and the pagination parameters are left entirely for the agent to infer from parameter names.

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 ('List direct group members') plus an explicit default scope, so an agent can distinguish it from a project-scoped member listing. It does not name the closest sibling (gitlab_list_project_members), so it falls short of full sibling differentiation.

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?

Gives a concrete motivation ('find reviewers or assignees by name') and states the condition for flipping include_inheritance=true, which is genuine when-to-use guidance. However, it never says when to prefer a different tool, and gives no guidance on the other filtering parameters (query, user_ids, skip_users) that would determine correct invocation.

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

Deploy Server