Skip to main content
Glama

list_projects

List GitLab projects you own or have access to. Filter by ownership and set the number of projects per page to manage your project overview.

Instructions

List GitLab projects.

Args:
    owned: If True, only show owned projects. If False, show all accessible projects.
    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
ownedNo
per_pageNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the 'list_projects' tool. It calls the GitLab API /projects endpoint with optional owned filter, formats project names, paths, and IDs into a bulleted list.
    @mcp.tool()
    async def list_projects(owned: bool = False, per_page: int = 20, token: str = None, ctx=None) -> str:
        """List GitLab projects.
        
        Args:
            owned: If True, only show owned projects. If False, show all accessible projects.
            per_page: Number of projects per page (max 100)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        per_page = min(per_page, 100)
        endpoint = f"/projects?membership=true&per_page={per_page}" + ("&owned=true" if owned else "")
        data = await make_gitlab_request(endpoint, ctx=ctx, token=token)
        
        if isinstance(data, dict) and "error" in data:
            return f"Error: {data['error']}"
        
        if not data:
            return "No projects found."
        
        projects = []
        for project in data:
            projects.append(f"• {project['name']} ({project['path_with_namespace']}) - ID: {project['id']}")
        
        return "\n".join(projects)
  • The @mcp.tool() decorator registers list_projects as an MCP tool named 'list_projects'.
    @mcp.tool()
  • Helper function used by list_projects (and all other tools) to make authenticated requests to the GitLab API. Handles token resolution from parameters, context headers, or environment variables, and builds the API URL.
    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, so the description carries full burden for behavioral disclosure. It only states the purpose and parameter meanings, but fails to mention that this is a read-only operation, pagination behavior (beyond per_page), authentication requirements beyond token, rate limits, or any side effects. The optional token leaves ambiguity about default auth.

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 concise with a clear purpose statement followed by a focused parameter list. Every sentence is necessary and adds value. It is front-loaded with the primary action and then enumerates parameters in a readable format. No redundancy or fluff.

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

Completeness3/5

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

Given the existence of an output schema, the description need not explain return values. However, with many sibling tools (search_projects, list_user_projects, etc.), it lacks guidance on when to choose this tool over others. The 'owned' parameter provides some scoping, but overall completeness is adequate but not thorough.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema provides no descriptions (0% schema description coverage), so the description must fully explain each parameter. It does so clearly: 'owned' with true/false semantics, per_page with max limit (added value beyond schema), token as optional, and ctx as auto-injected. This adds significant meaning beyond the schema.

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 GitLab projects' as a verb+resource combination. Among siblings, it distinguishes by being the most general listing tool, while others like search_projects, list_user_projects, list_group_projects, and list_starred_projects have more specific scopes.

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

Usage Guidelines3/5

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

The description explains the 'owned' parameter ('If True, only show owned projects. If False, show all accessible projects.') which gives some usage context. However, it does not explicitly state when to use this tool versus alternatives like search_projects, list_user_projects, or list_group_projects, nor does it provide any when-not-to-use guidance.

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