Skip to main content
Glama

create_branch

Creates a new branch in a GitLab project using the project ID, branch name, and an optional source reference. Automates branch creation for streamlined development workflows.

Instructions

Create a new branch.

Args:
    project_id: GitLab project ID
    branch_name: New branch name
    ref: Source branch/commit (default: main)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
branch_nameYes
refNomain
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function for the create_branch tool. It takes project_id, branch_name, ref (default 'main'), token, and ctx, then POSTs to the GitLab API to create a new branch.
    @mcp.tool()
    async def create_branch(project_id: int, branch_name: str, ref: str = "main", token: str = None, ctx=None) -> str:
        """Create a new branch.
        
        Args:
            project_id: GitLab project ID
            branch_name: New branch name
            ref: Source branch/commit (default: main)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {
            "branch": branch_name,
            "ref": ref
        }
        
        result = await make_gitlab_request(f"/projects/{project_id}/repository/branches", "POST", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error creating branch: {result['error']}"
        
        return f"Branch created: {result['name']} from {ref}"
  • The schema/type definition for the create_branch tool's inputs (project_id: int, branch_name: str, ref: str default 'main', optional token and ctx).
    async def create_branch(project_id: int, branch_name: str, ref: str = "main", token: str = None, ctx=None) -> str:
        """Create a new branch.
        
        Args:
            project_id: GitLab project ID
            branch_name: New branch name
            ref: Source branch/commit (default: main)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
  • The @mcp.tool() decorator registers create_branch as an MCP tool with the FastMCP server.
    @mcp.tool()
  • The make_gitlab_request helper function used by create_branch to make the actual HTTP POST request to the GitLab API for creating a branch.
    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 bears full responsibility. It mentions default ref but lacks details on error handling, idempotency, or authorization needs.

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, using a brief sentence followed by a bullet-style argument list. No wasted words.

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?

Despite having an output schema, the description does not explain return values or potential errors. Lacks information on prerequisites, permissions, or conflict behavior, making it incomplete for a create operation.

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?

Schema description coverage is 0%, but the description adds meaningful explanations for each parameter (e.g., 'GitLab project ID', 'New branch name'), going beyond just names and types.

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 'Create a new branch,' which is a specific verb and resource. It distinguishes from sibling tools like delete_branch or get_project_branches.

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 this tool versus alternatives (e.g., create_tag, create_commit). Missing context on prerequisites or preferred scenarios.

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