Skip to main content
Glama

get_repository_files

Retrieve files and directories from a GitLab project repository by providing project ID, optional path, and branch or tag reference.

Instructions

Get repository files and directories.

Args:
    project_id: GitLab project ID
    path: Directory path (optional)
    ref: Branch/tag reference (default: main)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
pathNo
refNomain
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_repository_files tool handler function. It is decorated with @mcp.tool(), takes project_id, path, ref, token, and ctx parameters. It calls the GitLab API endpoint /projects/{project_id}/repository/tree?path={path}&ref={ref} to list repository files and directories, then formats them with icons (📁 for directories, 📄 for files), limited to 20 items.
    @mcp.tool()
    async def get_repository_files(project_id: int, path: str = "", ref: str = "main", token: str = None, ctx=None) -> str:
        """Get repository files and directories.
        
        Args:
            project_id: GitLab project ID
            path: Directory path (optional)
            ref: Branch/tag reference (default: main)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        endpoint = f"/projects/{project_id}/repository/tree?path={path}&ref={ref}"
        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 files found."
        
        files = []
        for item in data[:20]:
            icon = "📁" if item['type'] == 'tree' else "📄"
            files.append(f"{icon} {item['name']}")
        return "\n".join(files)
  • The input schema for get_repository_files is defined implicitly via the function signature parameters: project_id (int, required), path (str, optional, default ''), ref (str, optional, default 'main'), token (str, optional), and ctx (optional). The docstring documents the Args as: project_id (GitLab project ID), path (Directory path), ref (Branch/tag reference, default: main).
    async def get_repository_files(project_id: int, path: str = "", ref: str = "main", token: str = None, ctx=None) -> str:
        """Get repository files and directories.
  • The tool is registered via the @mcp.tool() decorator on line 288, which uses FastMCP's tool registration mechanism to register the function as an MCP tool named 'get_repository_files'.
    @mcp.tool()
  • The make_gitlab_request helper function used by get_repository_files to make HTTP requests to the GitLab API. It handles token resolution (parameter, context headers, or environment variable), constructs the URL using GITLAB_URL, and makes async HTTP requests via httpx.
    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. It fails to disclose if the tool is read-only, what happens when path is omitted, or any permission requirements. Only parameter names and brief descriptions are given.

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 short and front-loaded with a clear summary. The bulleted list of parameters is structured and easy to parse, though slightly verbose for the parameter explanations.

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 the complexity of siblings, the description should clarify that 'get' means listing files and directories, not file contents. It omits this distinction and fails to fully specify the tool's behavior, leaving it somewhat 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 description coverage is 0%, so the description must compensate. It provides brief explanations for each parameter (e.g., 'GitLab project ID', 'Directory path (optional)'), which adds some meaning beyond the bare schema titles. However, details like valid formats or constraints are missing.

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 'Get repository files and directories' which identifies the verb and resource. However, it does not distinguish between listing files and getting file contents, especially given the sibling tool 'get_file_content'.

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 explicit guidance on when to use this tool vs alternatives like 'get_file_content', 'create_file', etc. The description merely lists parameters without any context about selection.

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