Skip to main content
Glama
harshmaur

GitLab MCP Server

by harshmaur

list_issue_discussions

Retrieve discussions and comments for a specific issue in a GitLab project to track conversation history and collaboration.

Instructions

List discussions for an issue in a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or URL-encoded path
issue_iidYesThe internal ID of the project issue
pageNoPage number for pagination (default: 1)
per_pageNoNumber of items per page (max: 100, default: 20)

Implementation Reference

  • Input schema for the 'list_issue_discussions' tool, defining parameters project_id and issue_iid with pagination options.
    export const ListIssueDiscussionsSchema = z.object({
      project_id: z.string().describe("Project ID or URL-encoded path"),
      issue_iid: z.number().describe("The internal ID of the project issue"),
    }).merge(PaginationOptionsSchema);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'List' implies a read operation, it doesn't disclose important behavioral traits like authentication requirements, rate limits, pagination behavior beyond what's in the schema, error conditions, or response format. The description is minimal and lacks operational context needed for safe invocation.

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 with zero waste. It's appropriately sized for this tool's complexity and front-loads the core purpose immediately. Every word earns its place without redundancy or unnecessary elaboration.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description is incomplete. It doesn't address what the tool returns (discussion format, structure), error handling, authentication needs, or operational constraints. The minimal description leaves significant gaps for an agent to understand how to properly use this tool.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain relationships between parameters, provide examples, or clarify edge cases. Baseline 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 ('List discussions') and target resource ('for an issue in a GitLab project'), providing a specific verb+resource combination. It distinguishes this tool from siblings like 'list_issues' or 'mr_discussions' by focusing specifically on issue discussions, though it doesn't explicitly contrast with similar tools.

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. It doesn't mention prerequisites, context for usage, or differentiate from potential overlapping tools like 'get_issue' (which might include discussions) or 'create_issue_note' (for adding to discussions).

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

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