Skip to main content
Glama
Sign In
@wanadev/mcp-gitlab

@wanadev/mcp-gitlab

by wanadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_member

Remove a user from a GitLab group or project. Dry run mode previews changes before execution to prevent accidental removal.

Instructions

Remove a user from a group or project. dry_run=true by default. This is destructive.

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": {
      "scope": "<scope>",
      "id": "<id>",
      "user_id": "<user_id>"
    },
    "name": "remove_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeYes'group' or 'project'
idYesGroup ID/path or numeric project ID
user_idYesNumeric user ID to remove
dry_runNoDry 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.

  1. First observedv1.8.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only provide readOnlyHint: false, so description carries burden. It adds that dry_run is true by default and labels tool as destructive, providing useful behavioral context beyond annotations.

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?

Two sentences, front-loaded with purpose, followed by critical safety warning. 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?

No output schema, so description should cover return values and prerequisites. It does not mention what the tool returns or error conditions. With 4 parameters and destructive nature, more context would help.

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 baseline is 3. Description reiterates dry_run default but adds little new meaning beyond schema descriptions for other parameters.

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 'Remove a user from a group or project', using a specific verb and resource, and distinguishes from sibling tools like add_group_member or update_member_access_level.

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 mentions dry_run=true by default and 'destructive', implying safety precautions, but does not explicitly state when to use this tool vs alternatives or when not to use it.

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

Deploy Server

Other Tools