GitLab MCP Server

get_users

Retrieve user details from GitLab by providing specific usernames to access profile information and manage team members.

Instructions

Get GitLab user details by usernames

Input Schema

TableJSON Schema

Name	Required	Description	Default
`usernames`	Yes	Array of usernames to search for

Implementation Reference

schemas.ts:205-207 (schema)
Input schema for the 'get_users' tool. Defines the expected input parameters: an array of usernames to retrieve user information for.
```
export const GetUsersSchema = z.object({
  usernames: z.array(z.string()).describe("Array of usernames to search for"),
});
```

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 16, 2025

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden; it offers only the verb 'Get' to imply a read. It does not disclose whether the operation is strictly read-only, how unknown usernames are handled, what fields are returned, or any authentication/rate-limit considerations.

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, front-loaded sentence with no filler. Every word earns its place, and the essential lookup mechanism ('by usernames') appears in the description.

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?

For a one-parameter lookup tool the description and schema allow invocation, but with no output schema and no annotations, the agent is left without a clear idea of what 'user details' will contain or how failures/partial matches behave. Some additional context on return shape would make it 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?

The schema describes the 'usernames' array fully (100% coverage), so the description adds little beyond restating that lookup is by usernames. No additional parameter semantics, formats, or constraints are needed, but none are provided 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?

States a specific verb ('Get'), resource ('GitLab user details'), and method ('by usernames'). It is clearly distinct from all sibling tools, which target projects, merge requests, pipelines, issues, milestones, releases, wiki pages, etc., and no other sibling targets users.

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 usage context is only implied: call this when you need user details and have usernames. There is no explicit when-to-use/when-not-to-use guidance and no mention of alternatives, though no sibling provides the same user-detail function.

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