Skip to main content
Glama

gitlab_resolve_discussion

Resolve GitLab merge request discussion threads when code review feedback has been addressed. Requires discussion ID and merge request number to close specific review conversations.

Instructions

Resolve a discussion thread Returns: Updated discussion Use when: Code review feedback addressed Required: Discussion ID from get_discussions

Related tools:

  • gitlab_get_merge_request_discussions: Find discussions

  • gitlab_add_merge_request_comment: Add resolution comment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject identifier (auto-detected if not provided) Type: integer OR string Format: numeric ID or 'namespace/project' Optional: Yes - auto-detects from current git repository Examples: - 12345 (numeric ID) - 'gitlab-org/gitlab' (namespace/project path) - 'my-group/my-subgroup/my-project' (nested groups) Note: If in a git repo with GitLab remote, this can be omitted
mr_iidYesMerge request number (IID - Internal ID) Type: integer Format: Project-specific MR number (without !) Required: Yes Examples: - 456 (for MR !456) - 7890 (for MR !7890) How to find: Look at MR URL or title - URL: https://gitlab.com/group/project/-/merge_requests/456 → use 456 - Title: "Add new feature (!456)" → use 456 Note: This is NOT the global MR ID
discussion_idYesDiscussion thread ID Type: string Required: Yes Format: SHA-like identifier How to get: From gitlab_get_merge_request_discussions Example: '6a9c1750b37d513a43987b574953fceb50b03ce7' Use case: Resolve specific discussion thread

Tool Definition Quality

Score is being calculated. Check back soon.

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/Vijay-Duke/mcp-gitlab'

If you have feedback or need assistance with the MCP directory API, please join our Discord server