gitlab-mcp

by wisesky0

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

list_mr_notes

Fetch comments from a GitLab merge request using project ID and MR IID. Supports pagination for large comment threads.

Instructions

MR 코멘트 목록 조회

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>",
      "mr_iid": "<mr_iid>"
    },
    "name": "list_mr_notes"
  }
}

Input Schema

Name	Required	Description
`page`	No	페이지 번호 (1부터)
`mr_iid`	Yes	MR iid
`instance`	No	대상 GitLab 인스턴스명 (생략 시 default)
`per_page`	No	페이지당 개수 (기본 20)
`project_id`	Yes	프로젝트 ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Jul 30, 2026

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 bears full responsibility for disclosing behavioral traits. It only says 'list' without mentioning pagination, ordering, or any side effects. Given the schema includes page and per_page, pagination is implied but not described.

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 extremely concise, consisting of a single Korean phrase. It front-loads the purpose but may be too brief. No wasted words, but could benefit from slight expansion.

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 absence of output schema and annotations, the description is incomplete. It does not explain return values, default behavior, or differentiate from closely related tools like list_mr_discussions. The agent would need to infer too much.

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?

Schema coverage is 100%, and all parameters are well-described in the input schema. The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 'MR 코멘트 목록 조회' clearly states it lists MR notes (comments). It distinguishes from sibling tools like list_mr_discussions and create_mr_note. However, it could be more specific about the scope (e.g., notes on a specific MR).

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any preconditions or context where it is applicable. The usage is implied but not explicit.

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