dev.mcp

Overview Schema Source Related Servers Discussions Admin

gitlab_save_merge_request

Create or update GitLab merge requests with project ID and optional title, branches, description, assignees, and reviewers. Provide an existing IID to update or leave blank to create.

Instructions

Creates (POST) or updates (PUT) a merge request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "gitlab_save_merge_request"
  }
}

Input Schema

Name	Required	Description
`draft`	No
`title`	No
`projectId`	Yes	Numeric ID or path with namespace, e.g. group/project.
`assigneeIds`	No
`description`	No
`reviewerIds`	No
`sourceBranch`	No
`targetBranch`	No
`mergeRequestIid`	No
`removeSourceBranch`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that the tool mutates state via POST/PUT, but it does not explain side effects, permissions required, what happens on update, required fields for creation, or response behavior. This is insufficient for a mutation tool with no annotation safety net.

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 a single, front-loaded sentence with no filler and includes the essential HTTP method distinction. It is concise and immediately communicates the core operation. However, it is so terse that it omits operationally important details, which slightly reduces the appropriateness of its size.

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?

This is a 10-parameter, dual-mode mutation tool with no annotations and no output schema, so the description needs to supply substantial context. It fails to explain the create-vs-update trigger, required parameters for each mode, or consequences of invocation. The description is not complete enough for an agent to reliably select and call the tool correctly.

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 only 10%, yet the description adds no parameter-level meaning. It does not indicate that mergeRequestIid selects update mode, that sourceBranch and targetBranch are likely needed for create, or how draft/removeSourceBranch behave. The agent must rely on schema property names alone for most parameters.

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 states a clear verb-resource pairing: 'Creates (POST) or updates (PUT) a merge request.' It names both the action and the target resource, and the HTTP methods reinforce the dual nature of the tool. There is no ambiguity with sibling tools like gitlab_list_merge_requests or gitlab_get_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?

No guidance is given about when to use this tool versus alternatives, or when the create path applies versus the update path. The description does not mention that mergeRequestIid likely distinguishes update from create, nor does it reference any sibling tool for comparison. An agent must infer usage entirely from the tool name and schema.

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

Deploy Server