GitLab MCP Server

create_issue

Create new issues in GitLab projects to track tasks, bugs, or feature requests with titles, descriptions, assignees, labels, and milestones.

Instructions

Create a new issue in a GitLab project

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>",
      "title": "<title>"
    },
    "name": "create_issue"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes	Project ID or complete URL-encoded path to project
`title`	Yes	Issue title
`description`	No	Issue description
`assignee_ids`	No	Array of user IDs to assign
`labels`	No	Array of label names
`milestone_id`	No	Milestone ID to assign

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 16, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It states the tool creates an issue but doesn't cover permissions required, rate limits, whether the operation is idempotent, what happens on failure, or the expected response format. This is inadequate for a mutation tool with zero annotation coverage.

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 directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place, with zero waste or redundancy.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain behavioral aspects like authentication needs, error handling, or return values, nor does it provide usage context relative to siblings. The high schema coverage helps with parameters, but overall context is lacking for effective tool selection and invocation.

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, clearly documenting all 6 parameters and their types. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as 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 issue') and resource ('in a GitLab project'), making the purpose immediately understandable. However, it doesn't differentiate this tool from similar sibling tools like 'create_issue_link' or 'create_issue_note', which would require more specific language about what constitutes an 'issue' versus other issue-related entities.

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 (e.g., needing project access), exclusions, or comparisons to sibling tools like 'update_issue' or 'list_issues', leaving the agent to infer usage context solely from the tool name.

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