Skip to main content
Glama

get_file_content

Retrieve the contents of a file in a GitLab repository using project ID, file path, and branch reference.

Instructions

Get content of a repository file.

Args:
    project_id: GitLab project ID
    file_path: Path to the file
    ref: Branch/tag reference (default: main)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
file_pathYes
refNomain
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'get_file_content' tool. Fetches file content from a GitLab repository using the GitLab API's repository files endpoint, URL-encodes the file path, decodes the base64-encoded content, and returns up to 2000 characters of the file content.
    @mcp.tool()
    async def get_file_content(project_id: int, file_path: str, ref: str = "main", token: str = None, ctx=None) -> str:
        """Get content of a repository file.
        
        Args:
            project_id: GitLab project ID
            file_path: Path to the file
            ref: Branch/tag reference (default: main)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        import urllib.parse
        encoded_path = urllib.parse.quote(file_path, safe='')
        endpoint = f"/projects/{project_id}/repository/files/{encoded_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']}"
        
        import base64
        try:
            content = base64.b64decode(data['content']).decode('utf-8')
            return f"File: {file_path}\n\n{content[:2000]}{'...' if len(content) > 2000 else ''}"
        except:
            return "Unable to decode file content"
  • Registration of 'get_file_content' as an MCP tool via the @mcp.tool() decorator on the async function.
    @mcp.tool()
    async def get_file_content(project_id: int, file_path: str, ref: str = "main", token: str = None, ctx=None) -> str:
  • Input schema/type signature for get_file_content: expects project_id (int), file_path (str), optional ref (str, default 'main'), optional token (str), and automatically injected ctx. Returns a string.
    async def get_file_content(project_id: int, file_path: str, ref: str = "main", token: str = None, ctx=None) -> str:
        """Get content of a repository file.
        
        Args:
            project_id: GitLab project ID
            file_path: Path to the file
            ref: Branch/tag reference (default: main)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
  • Helper function 'make_gitlab_request' used by get_file_content to make authenticated API requests 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 should disclose behavioral traits (e.g., authentication, rate limits, error handling). It only states 'get content' but omits details like token usage or response behavior. Basic action is clear but lacks depth.

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 extremely concise: a one-line summary followed by a parameter list. No redundant text, front-loaded purpose, efficient and scannable.

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 output schema exists, the description need not detail return values, but it doesn't mention that the tool returns file content. With 5 parameters and 2 required, the description covers main ones but lacks context on optional parameters like token effects.

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 no descriptions for parameters, but the description adds explanations for each, e.g., 'ref' with default, 'token' as optional. This adds meaning beyond the schema. Could be improved by clarifying token necessity or file_path format.

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 explicitly states 'Get content of a repository file', which clearly identifies the verb (get) and resource (content of a repository file). It distinguishes itself from sibling tools like create_file or update_file.

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?

The description does not provide any guidance on when to use this tool versus alternatives like get_repository_files (which lists files). No explicit when/when-not context is given.

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