Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

list_projects

Retrieve all projects within your Glitchtip organization to monitor error tracking across different applications and services.

Instructions

List all Glitchtip projects in the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that lists all Glitchtip projects in the organization by fetching from the API and returning JSON data.
    async listProjects() {
      const url = `${this.apiEndpoint}/api/0/organizations/${this.organizationSlug}/projects/`;
      
      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 projects: ${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 tool schema definition, including name, description, and empty input schema (no parameters required).
    {
      name: "list_projects",
      description: "List all Glitchtip projects in the organization",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • src/index.js:143-144 (registration)
    Registration of the tool in the dispatcher switch case within the CallToolRequestHandler.
    case "list_projects":
      return await this.listProjects();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all') but doesn't describe traits like pagination, rate limits, authentication needs, or what 'all' entails (e.g., if it returns a complete list or requires filtering). This is a significant gap for a list operation with zero annotation coverage.

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 directly states the tool's purpose without any waste. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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 simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It covers the basic purpose but lacks behavioral context (e.g., how results are returned), which is important for a list operation. Without annotations or output schema, more detail would improve completeness.

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 tool has 0 parameters, and schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as it doesn't introduce confusion or redundancy.

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 ('all Glitchtip projects in the organization'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_project' or 'list_issues', which might also retrieve project-related data, so it doesn't reach the highest score.

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' (for a single project) or 'list_issues' (which might include project context). It lacks explicit when-to-use or when-not-to-use instructions, leaving usage context implied at best.

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