Skip to main content
Glama

gitlab_list_project_members

Retrieve a list of members for a specified GitLab project by providing the project ID or URL-encoded path to manage access and collaboration.

Instructions

List members of a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesThe ID or URL-encoded path of the project

Implementation Reference

  • The handler function that implements the gitlab_list_project_members tool. It extracts the project_id from arguments, validates it, calls the usersGroupsManager.listProjectMembers method, and formats the response.
    export const listProjectMembers: ToolHandler = async (params, context) => {
      const { project_id } = params.arguments || {};
      if (!project_id) {
        throw new McpError(ErrorCode.InvalidParams, 'project_id is required');
      }
      
      const data = await context.usersGroupsManager.listProjectMembers(project_id as string | number);
      return formatResponse(data);
    };
  • The input schema definition for the gitlab_list_project_members tool, specifying the required project_id parameter.
    {
      name: 'gitlab_list_project_members',
      description: 'List members of a project',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'The ID or URL-encoded path of the project'
          }
        },
        required: ['project_id']
      }
    },
  • The tool registry mapping where gitlab_list_project_members is registered to the usersGroupsHandlers.listProjectMembers handler function.
    // Users and Groups tools
    gitlab_list_users: usersGroupsHandlers.listUsers,
    gitlab_get_user: usersGroupsHandlers.getUser,
    gitlab_list_groups: usersGroupsHandlers.listGroups,
    gitlab_get_group: usersGroupsHandlers.getGroup,
    gitlab_list_group_members: usersGroupsHandlers.listGroupMembers,
    gitlab_add_group_member: usersGroupsHandlers.addGroupMember,
    gitlab_list_project_members: usersGroupsHandlers.listProjectMembers,
    gitlab_add_project_member: usersGroupsHandlers.addProjectMember
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral insight. It implies a read-only operation ('List'), but doesn't disclose pagination, rate limits, authentication needs, or output format (e.g., list of user objects). For a tool with zero annotation coverage, this leaves critical gaps in understanding how it behaves.

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?

The description is a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it immediately scannable. Every word earns its place by conveying essential purpose without redundancy.

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?

Given no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't address behavioral aspects like pagination, error cases, or return format, leaving the agent with insufficient context for reliable use. For a list operation, output details are critical but missing.

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 description coverage is 100%, with the single parameter 'project_id' documented as 'The ID or URL-encoded path of the project'. The description adds no additional parameter context beyond the schema. According to guidelines, when coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 'List members of a project' clearly states the verb ('List') and resource ('members of a project'), making the purpose immediately understandable. It distinguishes from siblings like 'gitlab_list_group_members' by specifying 'project' scope. However, it lacks specificity about what 'members' entails (e.g., roles, access levels), preventing a perfect score.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing project access), contrast with 'gitlab_list_group_members' for group-level members, or suggest complementary tools like 'gitlab_get_user' for member details. The agent must infer usage from context alone.

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

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

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