gitlab-api

Approve merge request

gitlab_approve_merge_request

Approve a specific GitLab merge request using its project ID and merge request IID so the request can proceed through required approvals.

Instructions

Approve a specific merge request.

Args: **kwargs: Additional parameters for the request (e.g., project_id, merge_request_iid).

Returns: Response: A wrapper containing the original response and a MergeRequest model.

Raises: MissingParameterError: If the project_id or merge_request_iid is missing. ParameterError: If invalid parameters are provided.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_approve_merge_request"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`name`	No
`group_id`	No
`user_ids`	No
`group_ids`	No
`rule_type`	No
`project_id`	No
`report_type`	No
`approval_rule_id`	No
`merge_request_iid`	No
`approvals_required`	No
`protected_branch_ids`	No
`applies_to_all_protected_branches`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv27.3.13Oct 25, 2026

TDQS

C2.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already state readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the mutation profile is partially covered. The description adds useful return-wrapper and error details, but does not explain permissions, side effects, or idempotency beyond what the annotations say.

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 front-loaded with the core action and organized into Args, Returns, and Raises sections. It is efficient overall, though the kwargs examples add limited value.

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?

For a 13-parameter mutation tool with 0% schema description coverage and no output schema, the description is incomplete. It clarifies the return wrapper and two key parameters, but does not explain the many other parameters, required inputs, or permission requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, and the description only names project_id and merge_request_iid. It does not explain the remaining parameters or clarify why they exist for an approval action, leaving most parameter semantics undocumented.

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 states a specific verb and resource: 'Approve a specific merge request.' This is clear and distinguishable from most tools, though it does not explicitly contrast with close siblings such as gitlab_accept_merge_request or gitlab_unapprove_merge_request.

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 provides no guidance on when to use this tool versus alternatives like accepting or unapproving a merge request. It only lists error conditions, not usage context or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server