Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

list_issues

Retrieve and display error tracking issues from Glitchtip, allowing filtering by project and setting result limits to monitor and debug application errors effectively.

Instructions

List issues in the organization or a specific project (requires event:read scope)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of issues to return (default: 25)
project_slugNoOptional project slug to filter issues by project

Implementation Reference

  • The handler function that executes the list_issues tool logic by fetching issues from the Glitchtip API.
    async listIssues(args) {
      const { project_slug, limit = 25 } = args || {};
      
      let url;
      if (project_slug) {
        url = `${this.apiEndpoint}/api/0/projects/${this.organizationSlug}/${project_slug}/issues/?limit=${limit}`;
      } else {
        url = `${this.apiEndpoint}/api/0/organizations/${this.organizationSlug}/issues/?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 issues: ${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 description for the list_issues tool, registered in the ListTools response.
    {
      name: "list_issues",
      description: "List issues in the organization or a specific project (requires event:read scope)",
      inputSchema: {
        type: "object",
        properties: {
          project_slug: {
            type: "string",
            description: "Optional project slug to filter issues by project"
          },
          limit: {
            type: "number",
            description: "Maximum number of issues to return (default: 25)"
          }
        }
      }
    },
  • src/index.js:139-140 (registration)
    The switch case that registers and dispatches to the listIssues handler for the list_issues tool.
    case "list_issues":
      return await this.listIssues(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 of behavioral disclosure. It adds some context by specifying the required scope ('event:read'), which is useful for authentication needs. However, it does not describe other behavioral traits such as pagination behavior (implied by 'limit' parameter), rate limits, or what happens when no issues are found, leaving gaps in transparency.

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 sized and front-loaded, stating the core purpose and key requirement in a single sentence. Every part earns its place by clarifying scope and authentication, though it could be slightly more structured by separating usage notes from the main action.

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 filtering), no annotations, and no output schema, the description is partially complete. It covers the action, scope, and authentication need, but lacks details on output format, error handling, or how results are ordered. This leaves some gaps for an agent to understand full context.

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?

The input schema has 100% description coverage, so the schema already documents both parameters ('limit' and 'project_slug') adequately. The description does not add any meaning beyond what the schema provides, such as explaining how 'project_slug' relates to the organization or default behaviors. Baseline 3 is appropriate when 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 tool's purpose with a specific verb ('List') and resource ('issues'), and specifies the scope ('in the organization or a specific project'). It distinguishes from siblings like 'get_issue' (singular retrieval) and 'list_events' (different resource), though it doesn't explicitly contrast with 'list_projects' or 'list_teams'.

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 provides implied usage guidance by mentioning the required scope ('requires event:read scope'), which indicates when the tool can be used. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_issue' (for single issues) or 'list_projects' (for listing projects instead of issues), and does not specify exclusions or prerequisites beyond the scope.

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