Skip to main content
Glama
rokrokss
by rokrokss

list_issues

List GitLab issues using filters for scope, state, labels, and project to locate and manage relevant tasks.

Instructions

List issues (default: created by current user only; use scope='all' for all accessible issues)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for pagination (default: 1)
scopeNoReturn issues from a specific scope
stateNoReturn issues with a specific state
labelsNoArray of label names
searchNoSearch for specific terms
due_dateNoReturn issues that have the due date
per_pageNoNumber of items per page (max: 100, default: 20)
author_idNoReturn issues created by the given user ID
milestoneNoMilestone title
issue_typeNoFilter to a given type of issue. One of issue, incident, test_case or task
project_idNoProject ID or URL-encoded path (optional - if not provided, lists issues across all accessible projects)
assignee_idNoReturn issues assigned to the given user ID. user id or none or any
confidentialNoFilter confidential or public issues
iteration_idNoReturn issues assigned to the given iteration ID. None returns issues that do not belong to an iteration. Any returns issues that belong to an iteration.
created_afterNoReturn issues created after the given time
updated_afterNoReturn issues updated after the given time
created_beforeNoReturn issues created before the given time
updated_beforeNoReturn issues updated before the given time
author_usernameNoReturn issues created by the given username
assignee_usernameNoReturn issues assigned to the given username
with_labels_detailsNoReturn more details for each label

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv2.0.35

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does reveal a non-obvious default filter (created_by_me) and how to expand to all accessible issues, which is valuable. It does not mention pagination behavior, ordering, read-only nature, or response shape, leaving some behavioral gaps.

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, front-loaded sentence that states the core action and the most important behavioral caveat. There is no filler, and every clause contributes useful information.

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 a 21-parameter tool, no annotations, and no output schema, a one-sentence description is insufficient for fully correct invocation. It addresses scope defaults but omits return structure, pagination/ordering details, date format expectations, and how the many filter parameters interact.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by specifying the default scope behavior and showing how to override it with scope='all'. This is real additional semantic value, though it only covers one of 21 parameters.

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 verb and resource ('List issues') and conveys a key scoping behavior: by default only issues created by the current user are returned. It does not explicitly distinguish itself from siblings like my_issues or get_issue, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides useful usage context for the scope parameter, noting the default and how to get all accessible issues ('use scope=\'all\''). However, it gives no guidance about when to choose this tool over related siblings such as my_issues or get_issue, so tool selection is left mostly to inference.

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

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