Skip to main content
Glama
Alosies

GitLab MCP Server

by Alosies

delete_mr_discussion_note

Delete a note from a merge request discussion by specifying the project, merge request, discussion, and note IDs.

Instructions

Delete a note from a merge request discussion

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesThe ID of the note to delete
project_idYesProject ID or path
discussion_idYesThe ID of the discussion
merge_request_iidYesMerge request internal ID
Behavior2/5

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

The description merely states the deletion action without elaborating on effects (e.g., permanence, permissions, impact on the discussion). With no annotations, the description should carry this burden but fails to do so.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that immediately conveys the tool's purpose without extraneous words.

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?

Given the tool requires 4 parameters and has no output schema or annotations, the description should provide more context on behavior, permissions, or results, but it remains minimal.

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

Parameters3/5

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

The input schema has 100% description coverage for parameters, so the description does not need to add much. It adds no extra meaning beyond the schema, yielding a baseline score.

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 action 'Delete' and the resource 'note from a merge request discussion'. However, it does not differentiate from the sibling tool 'delete_mr_note', which might have overlapping functionality.

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 like 'delete_mr_note' or other discussion-related tools.

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/Alosies/gitlab-mcp-server'

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