Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

Group Members

list_group_members
Read-onlyIdempotent

Retrieve GitLab group members with their access levels, filtering by name or username if needed.

Instructions

List group members with access levels, optionally filtered by search term

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of members to retrieve
searchNoOptional search term to filter members by name or username
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
groupPathYesFull path of the group (e.g., "my-group" or "parent/child-group")
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description is consistent and adds minor behavioral context about optional filtering and access levels, but does not contradict 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?

Single sentence, front-loaded with verb and resource, no wasted words. Efficiently communicates the core purpose.

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?

Despite good schema parameter descriptions, the description omits details about return format and pagination behavior. For a list tool with no output schema, more context on the result structure or pagination would improve completeness.

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%, so parameters are well-documented. The description adds value by summarizing the output (access levels) and mentioning optional search, which provides a high-level understanding 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 verb 'List' and the resource 'group members', adding 'with access levels' and 'optionally filtered by search term'. This distinguishes it from sibling tools like list_iterations or get_group_projects.

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 vs alternatives or provide exclusions. While the parameter descriptions mention pagination trade-offs, the main description lacks guidance on usage context.

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

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