Skip to main content
Glama
Sign In
GitLab MCP Server

GitLab MCP Server

by harshmaur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

create_note

Add comments to GitLab issues or merge requests by specifying project, item type, ID, and content.

Instructions

Create a new note (comment) to an issue or 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": {
      "project_id": "<project_id>",
      "noteable_type": "<noteable_type>",
      "noteable_iid": "<noteable_iid>",
      "body": "<body>"
    },
    "name": "create_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID or namespace/project_path
noteable_typeYesType of noteable (issue or merge_request)
noteable_iidYesIID of the issue or merge request
bodyYesNote content

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states this is a creation operation, implying mutation, but lacks details on permissions required, whether notes are editable or deletable, rate limits, or response format. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by specifying the action and target, making it highly concise and well-structured.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral details (e.g., permissions, side effects) and doesn't explain return values or error conditions, leaving significant gaps for an AI agent to understand the tool fully.

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 schema description coverage is 100%, meaning all parameters are documented in the schema itself. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't clarify parameter interactions or usage examples). Baseline score of 3 is appropriate when the schema does the heavy lifting.

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 ('Create a new note') and the target resource ('to an issue or merge request'), which distinguishes it from sibling tools like create_issue or create_merge_request. However, it doesn't explicitly differentiate from create_issue_note and create_merge_request_note, which appear to be similar sibling tools, making it slightly less specific than a perfect score.

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 create_issue_note or create_merge_request_note, nor does it mention any prerequisites or exclusions. It only states what the tool does without contextual usage instructions.

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

Deploy Server

Other Tools