gitlab-api

Create issue

gitlab_create_issue

Creates a new issue in a GitLab project or group with fields for title, description, labels, assignees, milestone, and state.

Instructions

Create a new issue.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_create_issue"
  }
}

Input Schema

Name	Required	Description	Default
`data`	No
`page`	No
`state`	No
`title`	No
`labels`	No
`group_id`	No
`per_page`	No
`issue_iid`	No
`max_pages`	No
`project_id`	No
`description`	No
`state_event`	No
`assignee_ids`	No
`milestone_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

First observedv27.3.13Oct 25, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false, so the mutation and safety profile is covered structurally. The description adds nothing beyond that: no mention of required permissions, whether group_id vs. project_id selects the namespace, or that duplicate creates are possible given non-idempotency.

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

Conciseness2/5

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

The single sentence contains no waste but is under-specified rather than concise. Brevity here is a symptom of missing content, not of disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A 14-parameter, zero-required, zero-coverage mutation tool with no output schema needs the description to carry real weight, and this one carries none. An agent cannot determine which identifier parameter actually targets the namespace, what fields are honored on create, or what comes back.

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

Parameters1/5

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

Schema description coverage is 0% across 14 parameters, and the description compensates for none of it. It never mentions title, description, labels, assignee_ids, milestone_id, or the pagination-shaped parameters (page, per_page, max_pages) that are surprising on a create tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reads 'Create a new issue,' which is a verbatim restatement of the tool name gitlab_create_issue and title 'Create issue.' It conveys no scope, no target (project vs. group), and nothing to distinguish it from siblings like gitlab_create_epic, gitlab_create_merge_request, or gitlab_create_note.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent gets no help deciding between this and gitlab_create_note, gitlab_create_epic, or gitlab_update_issue for similar issue-shaped work.

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

Deploy Server