update_merge_request_note
Modify an existing merge request discussion thread note to update content or change resolution status in GitLab projects.
Instructions
Modify an existing merge request thread note
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_id | Yes | Project ID or complete URL-encoded path to project | |
| merge_request_iid | Yes | The IID of a merge request | |
| discussion_id | Yes | The ID of a thread | |
| note_id | Yes | The ID of a thread note | |
| body | No | The content of the note or reply | |
| resolved | No | Resolve or unresolve the note |
Implementation Reference
- schemas.ts:749-761 (schema)Zod schema defining the input parameters for the 'update_merge_request_note' tool. It extends ProjectParamsSchema and requires project_id, merge_request_iid, discussion_id, note_id, and optionally body or resolved for updating a note in a merge request discussion.export const UpdateMergeRequestNoteSchema = ProjectParamsSchema.extend({ merge_request_iid: z.number().describe("The IID of a merge request"), discussion_id: z.string().describe("The ID of a thread"), note_id: z.number().describe("The ID of a thread note"), body: z.string().optional().describe("The content of the note or reply"), resolved: z.boolean().optional().describe("Resolve or unresolve the note"), }) .refine(data => data.body !== undefined || data.resolved !== undefined, { message: "At least one of 'body' or 'resolved' must be provided", }) .refine(data => !(data.body !== undefined && data.resolved !== undefined), { message: "Only one of 'body' or 'resolved' can be provided, not both", });