Skip to main content
Glama

get_project_users

Retrieve all users who have access to a specified GitLab project. Provide the project ID to list authorized users.

Instructions

Get users with access to a project.

Args:
    project_id: GitLab project ID
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the 'get_project_users' tool. It calls GitLab API endpoint /projects/{project_id}/users and returns a formatted list of users with their name, username, and state.
    async def get_project_users(project_id: int, token: str = None, ctx=None) -> str:
        """Get users with access to a project.
        
        Args:
            project_id: GitLab project ID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = await make_gitlab_request(f"/projects/{project_id}/users", ctx=ctx, token=token)
        
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        
        if not data:
            return "No users found."
        
        users = []
        for user in data[:15]:
            users.append(f"• {user['name']} (@{user['username']}) - {user['state']}")
        
        return "\n".join(users)
  • The tool is registered via the @mcp.tool() decorator on line 1266, which is the standard FastMCP registration pattern used throughout this server.
    @mcp.tool()
    async def get_project_users(project_id: int, token: str = None, ctx=None) -> str:
Behavior2/5

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

Annotations are absent, so the description must disclose behavioral traits. It only restates the purpose ('get users') without mentioning permissions, rate limits, error handling, or output structure. Minimal behavioral context beyond purpose.

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 short and efficient, using one sentence plus a parameter list. It avoids unnecessary words, though the Args format could be integrated more elegantly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the description lacks context about the return format (e.g., user roles, pagination), error conditions, and the effect of the optional token. Incomplete for a tool with no annotations.

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 0%, requiring the description to explain parameters. The 'Args' block adds meaning: 'project_id' is a GitLab project ID, 'token' is an optional PAT, 'ctx' is auto-injected. This provides necessary context beyond the schema schema.

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?

The description clearly states the tool retrieves users with access to a project, which is a specific verb and resource. It is distinguishable from siblings like get_project (project info) and get_group_members (group-level), though not explicitly differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives, no prerequisites or exclusions. The description only states the basic function without context on usage conditions.

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/skmprb/gitlab-clone-mcp-server'

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