Skip to main content
Glama
zereight

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_project_events

Read-only

Retrieve project events filtered by date, action, or target type. Use to audit activity or track changes for a known GitLab project.

Instructions

List events for a project (before/after: YYYY-MM-DD). Use this for a known resource or result; choose the corresponding list or search tool when you need to discover multiple resources. 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
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
project_idYesProject ID or URL-encoded path
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. Changed2 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
+  "project_id"
+]
  7. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'does not mutate GitLab data.' It goes beyond annotations by disclosing error behavior: 'missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors.' This adds useful context that an agent cannot infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence, then provides usage boundaries and behavioral details. It is dense but efficient; the third sentence packs both error behavior and parameter conventions into one long sentence, but every clause carries meaningful information. Minor structural improvement could split that sentence, but it remains readable.

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?

For a read-only, single-project listing tool with 100% schema coverage, the description covers purpose, usage boundaries, error behavior, and identifier formatting. There is no output schema, but the description does not describe the shape of returned events; however, 'List events' implies a standard event list and the tool's safety profile is already covered by annotations. The missing return-shape detail is a minor gap rather than a blocker.

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?

The schema already has 100% description coverage for all 9 parameters, so the baseline is 3. The description adds extra value by explaining how to provide project_id or group_id ('numeric ID or complete URL-encoded path described by the schema') and by emphasizing that pagination fields should be used exactly as documented. This goes beyond the schema's individual 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 states a specific verb and resource ('List events for a project') and immediately disambiguates from discovery tools: 'Use this for a known resource or result; choose the corresponding list or search tool when you need to discover multiple resources.' This clearly distinguishes it from siblings like list_events and list_issues.

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

Usage Guidelines5/5

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

It explicitly defines when to use this tool ('for a known resource or result') and when not to ('choose the corresponding list or search tool when you need to discover multiple resources'). It also provides concrete guidance on providing identifiers and using pagination fields, leaving no ambiguity about invocation.

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