Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

list_events

Retrieve error events from a Glitchtip project to monitor and debug application issues. Specify the project slug to view recent events with configurable limits.

Instructions

List events for a specific project (requires event:read scope)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return (default: 25)
project_slugYesThe slug of the project

Implementation Reference

  • The handler function that implements the list_events tool logic: fetches events from Glitchtip API for the specified project.
    async listEvents(args) {
      const { project_slug, limit = 25 } = args || {};
      
      if (!project_slug) {
        return {
          content: [
            {
              type: "text",
              text: "Error: project_slug is required"
            }
          ]
        };
      }
      
      const url = `${this.apiEndpoint}/api/0/projects/${this.organizationSlug}/${project_slug}/events/?limit=${limit}`;
      
      try {
        const response = await fetch(url, {
          method: 'GET',
          headers: {
            'Authorization': `Bearer ${this.apiToken}`,
            'Accept': 'application/json'
          }
        });
        
        if (!response.ok) {
          const errorText = await response.text();
          return {
            content: [
              {
                type: "text",
                text: `Error fetching events: ${response.status} ${response.statusText}\n${errorText}`
              }
            ]
          };
        }
        
        const data = await response.json();
        
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(data, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Error: ${error.message}`
            }
          ]
        };
      }
    }
  • The input schema and metadata for the list_events tool, as returned by the ListTools handler.
    {
      name: "list_events",
      description: "List events for a specific project (requires event:read scope)",
      inputSchema: {
        type: "object",
        properties: {
          project_slug: {
            type: "string",
            description: "The slug of the project"
          },
          limit: {
            type: "number",
            description: "Maximum number of events to return (default: 25)"
          }
        },
        required: ["project_slug"]
      }
    },
  • src/index.js:141-142 (registration)
    The switch case in the CallToolRequestHandler that registers and dispatches calls to the listEvents handler.
    case "list_events":
      return await this.listEvents(args);
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the required 'event:read scope' for authentication, which is useful behavioral context. However, it lacks details on rate limits, pagination (beyond the 'limit' parameter), error handling, or what the return format looks like (e.g., list structure). The description adds some value but is incomplete for behavioral transparency.

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 a single, efficient sentence that front-loads the core purpose and includes essential context (scope requirement). There is zero waste, and every word earns its place, making it appropriately sized for this tool.

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?

Given the tool's moderate complexity (list operation with authentication), no annotations, and no output schema, the description is partially complete. It covers the purpose and scope requirement but lacks details on return values, error cases, or behavioral traits like pagination. It's adequate as a minimum viable description but has clear gaps.

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%, with clear descriptions for both parameters ('limit' and 'project_slug'). The description adds no additional parameter semantics beyond what the schema provides, such as format details for 'project_slug' or constraints on 'limit'. Baseline 3 is appropriate as the schema does the heavy lifting.

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 resource ('events'), specifying it's for a specific project. It distinguishes from potential siblings like 'list_issues' or 'list_projects' by focusing on events. However, it doesn't explicitly differentiate from hypothetical siblings like 'get_event' or 'search_events' that might exist elsewhere.

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?

The description implies usage context by mentioning 'for a specific project' and the required 'event:read scope', which suggests when authentication is needed. However, it doesn't provide explicit guidance on when to use this tool versus alternatives like 'list_issues' or 'get_project', nor does it mention exclusions or prerequisites beyond the scope requirement.

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/CleverMobi/glitchtip-mcp'

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