Skip to main content
Glama
Sign In
ttpears

GitLab MCP Server

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

My Events

list_my_events
Read-onlyIdempotent

Retrieve the authenticated user's GitLab activity feed—pushes, merge requests, comments, approvals, and issue actions—to review recent work.

Instructions

List the authenticated user's GitLab activity feed — pushes, MRs, comments, approvals, issue actions. Primary tool for "what did I just do". Requires user authentication.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based)
sortNoSort order (default desc — newest first)desc
afterNoOnly events after this date (YYYY-MM-DD)
scopeNoSet to "all" to include events from any project you have access to, not just your own authored events
actionNoFilter by action type
beforeNoOnly events before this date (YYYY-MM-DD)
per_pageNoResults per page
target_typeNoFilter by target resource type
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / userCredentials / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "accessToken": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "gitlabUrl": {
-        "format": "uri",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "accessToken": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "gitlabUrl": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Addedv1.15.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered externally. The description adds useful context that user authentication is required and what event categories come back, but says nothing about pagination behavior or volume, and "requires user authentication" sits slightly uneasily with the optional userCredentials parameter.

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?

Three short clauses with the resource and its contents front-loaded; no filler. The auth sentence is brief and earns its place as a prerequisite note.

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?

With nine optional parameters, four enums and no output schema, the description covers purpose and auth but omits any hint of the filtering/paging surface or result shape. It is adequate to identify the tool, but thin for a tool whose value depends on filter combination.

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% and four enum parameters are fully documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning about filters (action, target_type, scope, after/before) or paging beyond what the schema already states.

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

Purpose4/5

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

Names a specific verb and resource ("List the authenticated user's GitLab activity feed") and enumerates the event kinds returned (pushes, MRs, comments, approvals, issue actions). The scope word "authenticated user's" implicitly separates it from list_user_events and list_project_events, but it never names those siblings explicitly.

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?

"Primary tool for 'what did I just do'" gives a use-case cue, which is better than nothing. However, there is no when-not guidance and no routing to nearby alternatives such as list_user_events (other users), list_project_events (project-wide), or list_my_todos (actionable items), so the agent must infer selection.

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