Skip to main content
Glama

list_events

Retrieve and filter your GitLab activity history by date, action type, or target to monitor project changes and user interactions.

Instructions

List all events for the currently authenticated user. Note: before/after parameters accept date format YYYY-MM-DD only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoIf defined, returns events with the specified action type
target_typeNoIf defined, returns events with the specified target 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
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
sortNoDirection to sort the results by creation date. Default: desc
pageNoReturns the specified results page. Default: 1
per_pageNoNumber of results per page. Default: 20

Implementation Reference

  • Input schema definition for the 'list_events' MCP tool, mapping to GitLab's /events API endpoint for listing user events.
    export const ListEventsSchema = z.object({
      action: z.string().optional().describe("If defined, returns events with the specified action type"),
      target_type: z.enum(["epic", "issue", "merge_request", "milestone", "note", "project", "snippet", "user"]).optional().describe("If defined, returns events with the specified target type"),
      before: z.string().optional().describe("If defined, Returns events created before the specified date (YYYY-MM-DD format). To include events on 2025-08-29, use before=2025-08-30"),
      after: z.string().optional().describe("If defined, Returns events created after the specified date (YYYY-MM-DD format). To include events on 2025-08-29, use after=2025-08-28"),
      scope: z.string().optional().describe("Include all events across a user's projects"),
      sort: z.enum(["asc", "desc"]).optional().describe("Direction to sort the results by creation date. Default: desc"),
      page: z.number().optional().describe("Returns the specified results page. Default: 1"),
      per_page: z.number().optional().describe("Number of results per page. Default: 20"),
    });
  • Response schema for GitLab events used by the 'list_events' tool.
    export const GitLabEventSchema = z.object({
      id: z.coerce.string(),
      project_id: z.coerce.string(),
      action_name: z.string(),
      target_id: z.coerce.string().nullable(),
      target_iid: z.coerce.string().nullable(),
      target_type: z.string().nullable(),
      author_id: z.coerce.string(),
      target_title: z.string().nullable(),
      created_at: z.string(),
      author: GitLabEventAuthorSchema,
      author_username: z.string(),
      imported: z.boolean(),
      imported_from: z.string(),
    }).passthrough(); // Allow additional fields
  • The tool 'list_events' is listed and tested as part of the MCP readonly tools test suite.
    { name: 'list_events', category: 'event', required: false },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions date format constraints for before/after parameters but doesn't disclose pagination behavior (implied by page/per_page parameters), rate limits, authentication requirements beyond 'authenticated user', or what happens with large result sets. For a list tool with 8 parameters, this is inadequate.

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 appropriately brief with two sentences. The first sentence states the core purpose, and the second adds important constraint information. No wasted words, though it could be slightly more informative given the tool's complexity.

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

Completeness2/5

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

For a tool with 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return format, pagination behavior, error conditions, or how parameters interact. The agent must rely entirely on the input schema for parameter details with minimal guidance from the description.

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 schema fully documents all 8 parameters. The description adds only the date format constraint for before/after parameters, which is already partially covered in schema descriptions. It provides no additional context about parameter interactions, defaults, or usage patterns beyond what's in the schema.

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?

The description clearly states the verb 'List' and the resource 'events', specifying it's for the 'currently authenticated user'. It distinguishes from siblings like 'get_project_events' by focusing on user-specific events rather than project events. However, it doesn't explicitly contrast with all sibling read operations like 'list_issues' or 'list_merge_requests'.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_project_events' or other list tools. It mentions the user scope but doesn't explain when user events are needed over project events or other event sources. No exclusions or prerequisites are stated.

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

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