gitlab-api

Get issues

gitlab_get_issues

Read-onlyIdempotent

Retrieve GitLab issues and filter them by project, group, state, labels, assignee, or milestone to find and review relevant work items.

Instructions

Get list of issues. Can filter by project_id.

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_get_issues"
  }
}

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

C2.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. Beyond that the description adds only a filter hint and says nothing about pagination behavior (page, per_page, max_pages parameters exist), what happens with max_pages, or whether omitting project_id triggers a broad cross-project scan.

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

Conciseness3/5

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

Two short sentences with no filler, and the core purpose is front-loaded. However, this is under-specification rather than conciseness — the brevity costs the agent critical information about a 14-parameter tool.

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?

A 14-parameter listing tool with 0% schema coverage and no output schema needs the description to explain filtering, pagination, and scope. The description covers roughly one parameter, leaving the agent unable to construct a correct call beyond the simplest case.

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

Parameters2/5

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

Schema description coverage is 0% across 14 parameters, so the description carries the full burden and fails it: it explains only project_id. Meaningful semantics for state, labels, title, issue_iid, group_id, state_event, assignee_ids, milestone_id, page/per_page/max_pages, and the opaque `data` object are left entirely undocumented.

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

Purpose3/5

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

The verb+resource ("Get list of issues") is identifiable, but the description gives no basis for choosing it over close siblings such as gitlab_get_issue, gitlab_get_group_issues, or gitlab_get_milestone. The only scoping detail offered ("Can filter by project_id") understates the tool's actual reach since the schema exposes group_id, issue_iid, labels, state and more.

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 and no mention of alternatives. "Can filter by project_id" hints at a project-scoped listing, but an agent cannot tell from this text whether the tool works across all projects when project_id is omitted, or when it should prefer gitlab_get_group_issues instead.

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

Deploy Server