Skip to main content
Glama

delete_project

Delete a GitLab project permanently by providing its project ID. Optionally authenticate with a personal access token.

Instructions

Delete a GitLab project.

Args:
    project_id: GitLab project ID
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The delete_project tool handler function. Takes a project_id (int) and optional token/ctx, sends a DELETE request to GitLab API /projects/{project_id}, and returns a success or error message.
    async def delete_project(project_id: int, token: str = None, ctx=None) -> str:
        """Delete a GitLab project.
        
        Args:
            project_id: GitLab project ID
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        result = await make_gitlab_request(f"/projects/{project_id}", "DELETE", ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error deleting project: {result['error']}"
        
        return f"Project {project_id} deleted successfully"
  • The tool is registered as an MCP tool via the @mcp.tool() decorator on line 79, which registers delete_project with FastMCP.
    @mcp.tool()
    async def delete_project(project_id: int, token: str = None, ctx=None) -> str:
  • Input parameter schema: project_id (int, required), token (str, optional), ctx (optional, auto-injected).
    """Delete a GitLab project.
    
    Args:
        project_id: GitLab project ID
        token: GitLab Personal Access Token (optional)
        ctx: MCP context (automatically injected)
  • The make_gitlab_request helper function handles the actual HTTP DELETE request to the GitLab API, used by delete_project.
    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?

With no annotations, the description must disclose side effects, permissions, and idempotency. It only says 'Delete a GitLab project' without addressing irreversibility, required access levels, or impact on associated resources.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very brief (one line plus parameter list), which is efficient but lacks essential prose. The structure is clear with a heading and parameter descriptions, but it is under-specified for a destructive operation.

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?

For a delete operation with no annotations and 0% schema coverage, the description should explain return values (output schema exists), error conditions, and behavioral nuances. It fails to provide this context, making it incomplete.

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 coverage is 0%, but the description adds meaning: project_id is identified as 'GitLab project ID', token as 'Personal Access Token (optional)', ctx as 'automatically injected'. This adds value, though more detail (e.g., project ID format) would improve.

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 clearly states 'Delete a GitLab project', which is a specific verb-resource pair. It distinguishes from sibling tools like archive_project or update_project, but lacks detail on what deletion entails (e.g., permanent vs soft delete).

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 delete vs alternatives like archive_project. No prerequisites (e.g., permissions) or consequences (e.g., irreversibility) are mentioned, leaving the agent without decision context.

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