Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

User Issues

get_user_issues
Read-onlyIdempotent

Retrieve all issues assigned to a specific GitLab user using reliable GraphQL filtering. Supports pagination, state filters, and optional project scoping.

Instructions

Get all issues assigned to a specific user - uses proper GraphQL filtering for reliable results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of issues to retrieve
stateNoFilter by issue state (opened, closed, all)opened
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
usernameYesUsername to find issues for (e.g., "cdhanlon")
projectPathNoOptional: limit search to a specific project
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
Behavior3/5

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

Annotations already declare the tool as read-only and idempotent. The description adds that it uses 'proper GraphQL filtering for reliable results', which hints at efficiency but does not detail pagination, rate limits, or other behavioral traits beyond annotations.

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, clear sentence with no extraneous information. It front-loads the core purpose efficiently.

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?

Given the thorough schema documentation for all 7 parameters and the read-only annotations, the description is nearly complete. It lacks explicit mention of return format, but the tool name and common knowledge about issue listing compensate. Slight gap in explaining pagination behavior, but schema covers it.

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 coverage is 100%, so the description adds minimal value beyond the schema. The description does not elaborate on parameter semantics; it relies entirely on the schema's detailed parameter descriptions.

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 clearly states the tool retrieves issues assigned to a specific user, using a verb and resource pattern. It distinguishes from siblings like 'get_issues' by emphasizing user assignment and GraphQL filtering for reliability.

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 implies usage for user-specific issue queries, but does not explicitly state when to use it versus alternatives like 'get_issues' or 'search_issues'. No when-not-to-use guidance is provided.

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

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