Skip to main content
Glama

create_merge_request

Create a merge request in GitLab to propose code changes. Specify project ID, source and target branches, and a title to initiate the merge process.

Instructions

Create a merge request.

Args:
    project_id: GitLab project ID
    source_branch: Source branch
    target_branch: Target branch
    title: MR title
    description: MR description (optional)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
source_branchYes
target_branchYes
titleYes
descriptionNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the create_merge_request tool. It posts to GitLab API /projects/{project_id}/merge_requests with source_branch, target_branch, title, and description, then returns the created MR's IID, title, and URL.
    @mcp.tool()
    async def create_merge_request(project_id: int, source_branch: str, target_branch: str, title: str, description: str = "", token: str = None, ctx=None) -> str:
        """Create a merge request.
        
        Args:
            project_id: GitLab project ID
            source_branch: Source branch
            target_branch: Target branch
            title: MR title
            description: MR description (optional)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {
            "source_branch": source_branch,
            "target_branch": target_branch,
            "title": title,
            "description": description
        }
        
        result = await make_gitlab_request(f"/projects/{project_id}/merge_requests", "POST", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error creating merge request: {result['error']}"
        
        return f"Merge request created: !{result['iid']} - {result['title']}\nURL: {result['web_url']}"
  • Input schema/type definitions for create_merge_request: project_id (int), source_branch (str), target_branch (str), title (str), description (str, default ''), token (optional str), ctx (auto-injected context).
    @mcp.tool()
    async def create_merge_request(project_id: int, source_branch: str, target_branch: str, title: str, description: str = "", token: str = None, ctx=None) -> str:
        """Create a merge request.
        
        Args:
            project_id: GitLab project ID
            source_branch: Source branch
            target_branch: Target branch
            title: MR title
            description: MR description (optional)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
  • The @mcp.tool() decorator registers create_merge_request as an MCP tool on the FastMCP server instance named 'mcp'.
    @mcp.tool()
  • Helper function that handles the actual HTTP request to the GitLab API. It resolves the auth token (parameter > context headers > env var), builds the URL from GITLAB_URL env var, and makes the HTTP request with proper error handling.
    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 provided, so description carries full burden. It only lists parameters and indicates token is optional. Does not disclose mutation effects, required permissions, or any side effects beyond creation.

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?

Single sentence with a bullet list of parameters. Concise but sparse; no wasted words but could benefit from more structure or context. Not overly verbose.

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?

With 7 parameters (4 required) and no behavioral details, the description is incomplete. Output schema exists, so return values need not be explained, but critical context like token behavior, project existence checks, or success/failure states is missing.

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?

Input schema coverage is 0% (no descriptions in schema). Description adds brief meaning to each parameter (e.g., 'project_id: GitLab project ID'), which adds value beyond the schema's type-only definitions, but lacks details like constraints or format.

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?

Description clearly states 'Create a merge request' with a specific verb and resource. It distinguishes from siblings like 'merge_merge_request' (merge vs create) and 'get_merge_requests' (retrieve), though it doesn't explicitly differentiate.

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 vs alternatives like 'merge_merge_request'. No prerequisites or exclusions mentioned. The agent is left to infer usage from 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