@wanadev/mcp-gitlab

add_group_member

Add a user to a GitLab group by specifying group ID, user ID, and access level. Uses dry-run mode by default for safety preview before execution.

Instructions

Add a user to a group with a given access level. dry_run=true by default.

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>",
      "user_id": "<user_id>",
      "access_level": "<access_level>"
    },
    "name": "add_group_member"
  }
}

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.
`user_id`	Yes	Numeric user ID (resolve from search_users)
`access_level`	Yes	Access level: 10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner.
`expires_at`	No	Optional expiration date (YYYY-MM-DD)
`dry_run`	No	Dry run mode (default: true). When true, returns a preview of the action without executing it. Set to false only after user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.8.0Jun 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotation 'readOnlyHint: false' already indicates mutation. The description adds the default dry_run behavior, but does not disclose other behavioral traits like authorization requirements or side effects. No contradiction with annotations.

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?

The description is a single sentence with no wasted words. It effectively front-loads the primary action and key parameter (dry_run).

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?

The tool has no output schema, so the description could explain return values or error handling. For a simple mutation tool, the description is adequate but could be more 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 coverage is 100%, so the schema already describes all parameters. The description reinforces the dry_run default, but adds no additional meaning beyond the schema.

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 action ('Add a user to a group'), specifies the required parameter 'access level', and highlights the default 'dry_run=true'. This distinguishes it from sibling tools like 'add_project_member' and 'remove_member'.

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 description does not explicitly state when to use this tool versus alternatives (e.g., 'add_project_member' or 'remove_member'). However, the default dry_run mode provides implicit guidance for cautious usage.

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

Deploy Server