Skip to main content
Glama

delete_file

Delete a file from a GitLab repository by specifying project, file path, branch, and commit message. Remove files directly through the API for clean version control.

Instructions

Delete a file from repository.

Args:
    project_id: GitLab project ID
    file_path: Path to the file
    branch: Target branch
    commit_message: Commit message
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
file_pathYes
branchYes
commit_messageYes
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The delete_file tool handler - an MCP tool decorated async function that deletes a file from a GitLab repository via the GitLab API. It takes project_id, file_path, branch, commit_message, and optional token/ctx, then sends a DELETE request to the GitLab repository files API endpoint.
    async def delete_file(project_id: int, file_path: str, branch: str, commit_message: str, token: str = None, ctx=None) -> str:
        """Delete a file from repository.
        
        Args:
            project_id: GitLab project ID
            file_path: Path to the file
            branch: Target branch
            commit_message: Commit message
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        import urllib.parse
        encoded_path = urllib.parse.quote(file_path, safe='')
        data = {
            "branch": branch,
            "commit_message": commit_message
        }
        
        result = await make_gitlab_request(f"/projects/{project_id}/repository/files/{encoded_path}", "DELETE", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error deleting file: {result['error']}"
        
        return f"File deleted: {file_path} from branch {branch}"
  • The registration of delete_file as an MCP tool via the @mcp.tool() decorator.
    @mcp.tool()
    async def delete_file(project_id: int, file_path: str, branch: str, commit_message: str, token: str = None, ctx=None) -> str:
  • The make_gitlab_request helper function used by delete_file to make the actual HTTP DELETE request to the GitLab API.
    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 fully disclose behavior. It only states 'Delete a file' without explaining side effects (e.g., irreversible commit, permissions needed, branch target), which is insufficient for a destructive action.

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 with a single purpose line and a structured 'Args:' block. Including ctx, which is automatically injected, adds minor redundancy but overall it is well-organized and front-loaded.

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 presence of an output schema and no annotations, the description adequately covers parameter meanings but fails to describe behavioral context, return value expectations, or error scenarios, leaving some completeness gaps.

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

Parameters4/5

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

The input schema has 0% description coverage, so the description's parameter explanations (e.g., 'project_id: GitLab project ID') add crucial meaning beyond the schema titles. However, it lacks constraints like expected formats or allowed values.

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 'Delete a file from repository,' providing a specific verb and resource. This distinguishes it from siblings like create_file, update_file, delete_branch, etc., which are present in the tool list.

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 is given on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction for appropriate usage.

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