Skip to main content
Glama

list_group_projects

Fetch a list of all projects within a specified GitLab group by providing the group name. Supports pagination with a configurable per-page limit.

Instructions

List projects in a group by group name.

Args:
    group_name: GitLab group name or path
    per_page: Number of projects per page (max 100)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_nameYes
per_pageNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Tool registered via @mcp.tool() decorator on the async function 'list_group_projects'. Registration is implicit through FastMCP's decorator pattern.
    @mcp.tool()
    async def list_group_projects(group_name: str, per_page: int = 50, token: str = None, ctx=None) -> str:
  • Handler function for 'list_group_projects'. Takes group_name, per_page, optional token and ctx. Calls GitLab API /groups/{group_name}/projects to list all projects in a group, returning formatted output.
    @mcp.tool()
    async def list_group_projects(group_name: str, per_page: int = 50, token: str = None, ctx=None) -> str:
        """List projects in a group by group name.
        
        Args:
            group_name: GitLab group name or path
            per_page: Number of projects per page (max 100)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        import urllib.parse
        encoded_name = urllib.parse.quote(group_name, safe='')
        per_page = min(per_page, 100)
        data = await make_gitlab_request(f"/groups/{encoded_name}/projects?per_page={per_page}", ctx=ctx, token=token)
        
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        
        if not data:
            return f"No projects found in group '{group_name}'."
        
        projects = []
        for project in data:
            projects.append(f"• {project['name']} ({project['path']}) - ID: {project['id']}")
        
        return f"Projects in group '{group_name}':\n" + "\n".join(projects)
  • Input schema via type hints and docstring: group_name (str, required), per_page (int, default 50, max 100), token (optional str), ctx (automatically injected MCP context). Output is a formatted string.
    async def list_group_projects(group_name: str, per_page: int = 50, token: str = None, ctx=None) -> str:
        """List projects in a group by group name.
        
        Args:
            group_name: GitLab group name or path
            per_page: Number of projects per page (max 100)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
  • Helper function make_gitlab_request used by list_group_projects to make authenticated HTTP requests to GitLab API v4.
    async def make_gitlab_request(endpoint: str, method: str = "GET", data: dict = None, ctx=None, token: str = None) -> dict[str, Any] | None:
        """Make a request to GitLab API with proper error handling."""
        # Priority: 1. Explicit token parameter, 2. Context headers, 3. Environment variable
        
        # If no explicit token provided, try to get from context
        if not token and ctx and hasattr(ctx, 'request_context') and ctx.request_context:
            # Try to get from request headers
            if hasattr(ctx.request_context, 'headers'):
                token = ctx.request_context.headers.get('GITLAB_TOKEN')
        
        # Fallback to environment variable
        if not token:
            token = os.getenv("GITLAB_TOKEN")
        
        if not token:
            return {"error": "GitLab token not provided. Please provide a token parameter, GITLAB_TOKEN in the request headers, or set the environment variable."}
        
        # Get GitLab URL (from context or environment)
        gitlab_url = os.getenv("GITLAB_URL", "https://gitlab.com")
        
        headers = {
            "PRIVATE-TOKEN": token,
            "Content-Type": "application/json"
        }
        
        url = f"{gitlab_url}/api/v4{endpoint}"
        
        async with httpx.AsyncClient() as client:
            try:
                if method == "GET":
                    response = await client.get(url, headers=headers, timeout=30.0)
                elif method == "POST":
                    response = await client.post(url, headers=headers, json=data, timeout=30.0)
                elif method == "PUT":
                    response = await client.put(url, headers=headers, json=data, timeout=30.0)
                elif method == "DELETE":
                    response = await client.delete(url, headers=headers, timeout=30.0)
                
                response.raise_for_status()
                return response.json() if response.content else {"success": True}
            except Exception as e:
                return {"error": str(e)}
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as read-only nature, pagination mechanics, rate limits, or idempotency. The agent cannot infer safety or side effects from the description alone.

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 concise and front-loaded with the main purpose. The arg list is clearly formatted. Every sentence serves a purpose, though it could be slightly more terse.

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 numerous sibling tools (over 50), the description is incomplete: it lacks disambiguation, behavioral transparency, and comprehensive parameter guidance. The presence of an output schema partially compensates, but overall context is insufficient.

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?

With 0% schema description coverage, the description adds meaning by explaining parameters: 'group_name: GitLab group name or path', 'per_page: Number of projects per page (max 100)', and 'ctx: MCP context (automatically injected)'. However, it does not specify valid formats or constraints beyond max per_page.

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 'List projects in a group by group name', specifying the verb (List), resource (projects), and qualifier (in a group by group name). This distinguishes it from sibling tools like 'list_projects' (all projects) and 'list_user_projects'.

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 like 'list_projects', 'list_groups', or 'search_projects'. The description does not mention when this tool is appropriate or when other tools should be preferred.

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