Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_events

Read-only

List user events from GitLab with date, action, or target filters. Pagination controls page and page size; results default to newest first.

Instructions

List events for the authenticated user (before/after: YYYY-MM-DD). Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect. It is read-only and does not mutate GitLab data; missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. When project_id or group_id is accepted, provide the numeric ID or complete URL-encoded path described by the schema; use required identifiers and pagination fields exactly as documented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoReturns the specified results page. Default: 1
sortNoDirection to sort the results by creation date. Default: desc
afterNoIf defined, Returns events created after the specified date (YYYY-MM-DD format). To include events on 2025-08-29, use after=2025-08-28
scopeNoInclude all events across a user's projects
actionNoIf defined, returns events with the specified action type
beforeNoIf defined, Returns events created before the specified date (YYYY-MM-DD format). To include events on 2025-08-29, use before=2025-08-30
jmespathNoOptional JMESPath expression filtering the JSON result before return.
per_pageNoNumber of results per page. Default: 20
target_typeNoIf defined, returns events with the specified target type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Addedv2.1.18
  3. Removedv2.1.14
  4. Addedv2.1.11
  5. Removedv2.1.10
  6. Changed1 schema field changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
  7. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

The description states 'It is read-only and does not mutate GitLab data' and enumerates error conditions (missing resources, invalid identifiers, insufficient permission, rate limits). This goes beyond the readOnlyHint annotation by specifying how failures are surfaced, which helps an agent anticipate outcomes.

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?

The purpose is front-loaded and the main usage note is efficient. However, the sentence about project_id/group_id references parameters absent from the schema, so it is filler that could mislead an agent and should be removed. This prevents the description from earning full marks for conciseness.

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?

For a tool with 9 parameters and no output schema, the description covers usage, safety, and error behavior, but it leaves gaps. It does not clarify the relationship with the get_project_events sibling, and the project_id/group_id sentence is irrelevant to this tool's schema. An agent would still rely heavily on the schema for invocation details.

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 adds generic guidance about project_id/group_id and pagination fields, but those identifiers are not in the schema, making the guidance potentially confusing rather than additive. It does not meaningfully enrich the already-documented parameter semantics.

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 opens with 'List events for the authenticated user' which clearly identifies the verb, resource, and scope. It explicitly distinguishes itself from sibling get tools by instructing to 'choose the corresponding get tool when you already know the single resource to inspect,' making it unambiguous as a collection-oriented list tool.

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?

It provides a clear when-to-use guideline: 'Use this for a collection of resources' and an exclusion: 'choose the corresponding get tool when you already know the single resource to inspect.' However, it does not name specific siblings like get_project_events, so an agent might still need to infer the exact alternative for project-scoped events.

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

Deploy Server

Other Tools