Skip to main content
Glama

list_issues

Fetch and filter GitLab issues by state, milestone, label, assignee, or search query. Returns clean summaries instead of raw objects to reduce context usage.

Instructions

List and filter issues by state, milestone, label, assignee, or search with clean summaries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesPage number for pagination
sortYesSort directiondesc
stateYesFilter by issue state (default: all)all
labelsNoFilter by label names (comma-separated or array)
searchNoSearch query matching issue title or description
verboseYesIf true, returns full raw GitLab objects instead of clean summaries
order_byYesField to sort bycreated_at
per_pageYesItems per page (default: 20, max: 100)
author_idNoFilter by author user ID
milestoneNoFilter by milestone title, or 'None' for issues without milestones, or 'Any'
project_idYesProject numeric ID (e.g. 31) or namespace path (e.g. 'group/project-name'). URL-encoding is handled automatically.
assignee_idNoFilter by assignee user ID
milestone_idNoFilter by numeric milestone ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It hints at output format with 'clean summaries,' but does not state that this is a read-only operation, whether authentication or specific permissions are required, rate-limit behavior, or pagination defaults.

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?

A single front-loaded sentence states the verb, resource, filter categories, and output style with no wasted words. Every phrase contributes to identifying or understanding the tool.

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

Completeness4/5

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

The schema is comprehensive and covers all parameters, so the description does not need to repeat them. It clearly communicates the tool's purpose and main filtering capabilities, though it omits some detail about output beyond 'clean summaries' and gives no usage context.

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 13 parameters thoroughly. The description lists several filter axes (state, milestone, label, assignee, search), but adds no syntax, format, or behavioral meaning beyond what the schema provides.

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

Purpose5/5

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

The description states a specific verb and resource: 'List and filter issues.' It also names the primary filter dimensions and the output style, which clearly separates this tool from get_issue, create_issue, and update_issue.

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?

No guidance is given on when to use this tool versus alternatives, how to choose between filters and search, or when to use pagination or verbose mode. The intended usage is implied by the verb 'List,' but no explicit context or exclusions are provided.

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