Skip to main content
Glama

merge_merge_request

Merge a merge request in GitLab by providing project ID and merge request IID, with an optional custom commit message.

Instructions

Merge a merge request.

Args:
    project_id: GitLab project ID
    merge_request_iid: Merge request IID
    merge_commit_message: Custom merge commit message (optional)
    token: GitLab Personal Access Token (optional)
    ctx: MCP context (automatically injected)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
merge_request_iidYes
merge_commit_messageNo
tokenNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for the 'merge_merge_request' tool. Accepts project_id, merge_request_iid, optional merge_commit_message, token, and ctx. Calls GitLab API PUT endpoint to merge the specified merge request.
    @mcp.tool()
    async def merge_merge_request(project_id: int, merge_request_iid: int, merge_commit_message: str = "", token: str = None, ctx=None) -> str:
        """Merge a merge request.
        
        Args:
            project_id: GitLab project ID
            merge_request_iid: Merge request IID
            merge_commit_message: Custom merge commit message (optional)
            token: GitLab Personal Access Token (optional)
            ctx: MCP context (automatically injected)
        """
        data = {}
        if merge_commit_message:
            data["merge_commit_message"] = merge_commit_message
        
        result = await make_gitlab_request(f"/projects/{project_id}/merge_requests/{merge_request_iid}/merge", "PUT", data, ctx=ctx, token=token)
        
        if isinstance(result, dict) and "error" in result:
            return f"Error merging MR: {result['error']}"
        
        return f"Merge request !{merge_request_iid} merged successfully"
  • The tool is registered via the @mcp.tool() decorator on the merge_merge_request async function.
    @mcp.tool()
    async def merge_merge_request(project_id: int, merge_request_iid: int, merge_commit_message: str = "", token: str = None, ctx=None) -> str:
  • Helper function used by merge_merge_request to make HTTP requests to the GitLab API. Handles token resolution, HTTP method dispatch, and 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 exist, and the description does not disclose behavioral traits like permissions required, destructive nature, or potential side effects (e.g., pipeline triggers). The description simply states the 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 structured as a brief docstring with a list of parameters. It is concise and easy to scan, though the parameter list could be formatted more compactly.

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?

An output schema exists (not shown), so return values need not be explained. However, the description lacks context on error handling, merge conditions, or how to interpret the result, making it incomplete for a merge 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?

The schema descriptions are minimal (only titles and types), but the tool description adds contextual docstrings for each parameter, explaining what they represent (e.g., 'GitLab project ID'). This adds value beyond the schema.

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 the verb and resource: 'Merge a merge request.' It is specific but does not differentiate from sibling tools like 'create_merge_request' or 'close_issue', which would enhance clarity.

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 provided on when to use this tool versus alternatives, such as when a merge request is ready for merging, or prerequisites like approvals or CI status.

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