Skip to main content
Glama

gitlab_get_group

Retrieve detailed information about a specific GitLab group by providing its ID or URL-encoded path. This tool is part of the GitLab MCP Server, enabling efficient group management and operations.

Instructions

Get details of a specific group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesThe ID or URL-encoded path of the group

Implementation Reference

  • The handler function that implements the core logic for the 'gitlab_get_group' tool. It extracts the group_id from parameters, validates it, calls the usersGroupsManager to fetch the group, and formats the response.
    export const getGroup: ToolHandler = async (params, context) => {
      const { group_id } = params.arguments || {};
      if (!group_id) {
        throw new McpError(ErrorCode.InvalidParams, 'group_id is required');
      }
      
      const data = await context.usersGroupsManager.getGroup(group_id as string | number);
      return formatResponse(data);
    };
  • The input schema definition for the 'gitlab_get_group' tool, specifying the required 'group_id' parameter.
    {
      name: 'gitlab_get_group',
      description: 'Get details of a specific group',
      inputSchema: {
        type: 'object',
        properties: {
          group_id: {
            type: 'string',
            description: 'The ID or URL-encoded path of the group'
          }
        },
        required: ['group_id']
      }
    },
  • The registration mapping in the toolRegistry that associates the 'gitlab_get_group' tool name with its handler function from usersGroupsHandlers.
    gitlab_get_group: usersGroupsHandlers.getGroup,
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 burden of behavioral disclosure. It only states the basic action ('get details') without mentioning critical aspects like authentication requirements, rate limits, error handling, or what 'details' include (e.g., metadata, permissions). This is inadequate for a tool with no annotation coverage.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 the lack of annotations and output schema, the description is incomplete. It does not explain what 'details' are returned (e.g., group name, ID, members), potential side effects, or error conditions. For a tool with no structured output or behavioral hints, more context is needed to guide the agent effectively.

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 input schema has 100% description coverage, with 'group_id' clearly documented as 'The ID or URL-encoded path of the group'. The description does not add any extra meaning beyond this, such as examples or format details. Given the high schema coverage, a baseline score of 3 is appropriate.

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 'Get details of a specific group' clearly states the action (get) and resource (group), making the purpose immediately understandable. However, it does not differentiate from sibling tools like 'gitlab_get_project' or 'gitlab_get_user', which follow a similar pattern, so it lacks sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not specify if this is for retrieving metadata versus listing groups (as in 'gitlab_list_groups'), nor does it mention prerequisites like authentication or group access. This leaves the agent without context for tool selection.

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