Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

My Todos

list_my_todos
Read-onlyIdempotent

List your GitLab to-do items, such as pending merge requests, issues, and review requests. Filter by state, target type, or project to focus on specific tasks.

Instructions

List the authenticated user's GitLab to-do items (notifications about issues, MRs, mentions, reviews requested, etc.). Filter by state, action, target type, or group/project. Requires user authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order — e.g. CREATED_DESC (default on server), CREATED_ASC, UPDATED_DESC, UPDATED_ASC.
typeNoFilter by target type — e.g. Issue, MergeRequest, Epic, Commit, DesignManagement::Design, AlertManagement::Alert
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 todos to retrieve
stateNoFilter by todo state: pending (default), done, or allpending
actionNoFilter by todo action — e.g. assigned, mentioned, build_failed, marked, approval_required, unmergeable, directly_addressed, review_requested
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).
authorIdsNoFilter by todo authors. Accepts numeric user IDs or full gid://gitlab/User/N strings.
groupPathNoLimit to a group by full path (e.g. "my-org/platform"). Resolved to a node GID server-side before filtering.
isSnoozedNoFilter by snooze state: true → only snoozed, false → only non-snoozed.
projectPathNoLimit to a project by full path (e.g. "my-org/my-repo"). Resolved to a node GID server-side before filtering.
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
Behavior5/5

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive. The description adds that it requires user authentication and lists the authenticated user's items. No contradictions. The description provides additional behavioral context beyond the annotations, such as the scope of items (notifications) and filtering options.

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 two sentences, front-loaded with the core purpose and enriched with filter categories and auth requirement. Every sentence adds value, and there is no fluff.

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

Completeness3/5

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

No output schema is present, and the description does not explain the return format or pagination behavior, which is important given the pagination parameters (after, first) and the complex fetchAll option. The schema descriptions cover these, but the tool description itself leaves a gap in how to use pagination reliably.

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 baseline is 3. The description provides a high-level summary of filterable fields but does not add significant new meaning beyond the schema's detailed param descriptions. It helps orient the user but does not compensate for gaps.

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 verb 'List', the resource 'the authenticated user's GitLab to-do items', and includes examples of typical items (issues, MRs, mentions, etc.). It distinguishes itself from sibling tools like mark_todo_done and restore_todo by focusing on listing.

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

Usage Guidelines4/5

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

The description mentions that authentication is required, which is a usage prerequisite. It also outlines filtering capabilities (state, action, target type, group/project). However, it does not explicitly state when not to use this tool or name alternatives, though the sibling context makes it clear that this is the listing tool.

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