Skip to main content
Glama

gitlab_get_group

Retrieve detailed group information from GitLab including metadata, settings, statistics, and optionally the first page of projects.

Instructions

Get detailed group information Returns: Complete group metadata, settings, statistics Use when: Need full group details, checking configuration, counting projects Optional: Include first page of projects with with_projects=true

Example response: { "id": 123, "name": "My Group", "full_path": "parent-group/my-group", "description": "Group for team projects", "visibility": "private", "projects_count": 15, "created_at": "2023-01-01T00:00:00Z", "web_url": "https://gitlab.com/groups/my-group" }

Related tools:

  • gitlab_list_groups: Browse available groups

  • gitlab_list_group_projects: List all projects in group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup identifier Type: integer OR string Format: numeric ID or 'group/subgroup' path Required: Yes Examples: - 456 (numeric ID) - 'my-group' (group path) - 'parent-group/sub-group' (nested group path)
with_projectsNoInclude projects in group response Type: boolean Default: false Options: - true: Include first page of projects - false: Only group metadata Note: Adds project list to response (limited to first 20)

Implementation Reference

  • The main handler function that implements the gitlab_get_group tool logic. Extracts group_id (required) and with_projects (optional) from arguments, then calls the GitLabClient.get_group method.
    def handle_get_group(client: GitLabClient, arguments: Optional[Dict[str, Any]]) -> Dict[str, Any]:
        """Handle getting single group"""
        group_id = require_argument(arguments, "group_id")
        with_projects = get_argument(arguments, "with_projects", False)
        
        return client.get_group(group_id, with_projects=with_projects)
  • The input schema definition for the gitlab_get_group tool, specifying required group_id (string) and optional with_projects (boolean). Used for tool validation and documentation.
    types.Tool(
        name=TOOL_GET_GROUP,
        description=desc.DESC_GET_GROUP,
        inputSchema={
            "type": "object",
            "properties": {
                "group_id": {"type": "string", "description": desc.DESC_GROUP_ID},
                "with_projects": {"type": "boolean", "description": desc.DESC_WITH_PROJECTS, "default": False}
            },
            "required": ["group_id"]
        }
    ),
  • Registration of the handle_get_group function to the TOOL_GET_GROUP ("gitlab_get_group") tool name in the TOOL_HANDLERS dictionary, which is used by server.py to dispatch tool calls.
    TOOL_GET_GROUP: handle_get_group,
  • Constant definition mapping the tool name string "gitlab_get_group" to TOOL_GET_GROUP, used consistently across handler registration, schema definitions, and server imports.
    TOOL_GET_GROUP = "gitlab_get_group"
Behavior4/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. It discloses that the tool returns 'complete group metadata, settings, statistics' and includes an example response, which adds context about output format. However, it doesn't mention behavioral traits like rate limits, authentication needs, or error handling, leaving some gaps 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 well-structured with sections like 'Returns', 'Use when', 'Optional', and 'Related tools', making it easy to scan. Each sentence adds value without waste, such as clarifying usage and providing an example, resulting in an efficient and front-loaded presentation.

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

Completeness4/5

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

Given no annotations and no output schema, the description compensates well by including an example response and usage guidelines. It covers the tool's purpose, when to use it, and related tools, but lacks details on error cases or performance limits, which could be useful for a read operation with no structured output schema.

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%, so the schema already documents both parameters thoroughly. The description adds minimal value by mentioning 'with_projects=true' includes 'first page of projects', but this is largely redundant with the schema's detailed description. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Get' and resource 'detailed group information', specifying it returns 'complete group metadata, settings, statistics'. It distinguishes from siblings like 'gitlab_list_groups' (browse groups) and 'gitlab_list_group_projects' (list projects), making the purpose specific and differentiated.

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

Usage Guidelines5/5

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

The 'Use when' section explicitly states scenarios: 'Need full group details, checking configuration, counting projects'. It also names related tools as alternatives, providing clear guidance on when to use this tool versus others, such as for detailed info rather than browsing or listing projects.

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

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