Skip to main content
Glama
CleverMobi

Glitchtip MCP Server

by CleverMobi

list_teams

Retrieve all teams within your Glitchtip organization to manage team access, permissions, and project assignments for error tracking and monitoring.

Instructions

List all teams in the organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_teams' tool. It makes a GET request to the Glitchtip API endpoint for the organization's teams, handles errors, and returns the JSON response as text content.
    async listTeams() {
      const url = `${this.apiEndpoint}/api/0/organizations/${this.organizationSlug}/teams/`;
      
      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 teams: ${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}`
            }
          ]
        };
      }
    }
  • src/index.js:136-153 (registration)
    The request handler switch statement that dispatches 'list_teams' calls to the listTeams() method.
    switch (name) {
      case "get_issue":
        return await this.getIssue(args);
      case "list_issues":
        return await this.listIssues(args);
      case "list_events":
        return await this.listEvents(args);
      case "list_projects":
        return await this.listProjects();
      case "get_project":
        return await this.getProject(args);
      case "get_organization":
        return await this.getOrganization();
      case "list_teams":
        return await this.listTeams();
      default:
        throw new Error(`Unknown tool: ${name}`);
    }
  • Tool registration including name, description, and input schema (no required parameters). This is part of the tools list provided to the MCP server.
    {
      name: "list_teams",
      description: "List all teams in the organization",
      inputSchema: {
        type: "object",
        properties: {}
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states it's a list operation but doesn't mention whether it's paginated, sorted, filtered, or if it requires specific permissions. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it behaves.

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 with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple list operation with no parameters.

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?

For a zero-parameter list tool with no output schema, the description covers the basic purpose adequately. However, without annotations or output schema, it doesn't address behavioral aspects like pagination, sorting, or permissions that would help an agent use it correctly in context.

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 zero parameters, and schema description coverage is 100% (though empty). The description doesn't need to explain parameters, and it appropriately doesn't mention any. A baseline of 4 is appropriate for zero-parameter tools when the description doesn't mislead about parameters.

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 teams in the organization'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_organization' or 'list_projects', which might also return team-related information in some contexts.

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_organization' (which might include team data) or 'list_projects' (which could be related). There's no mention of prerequisites, context, or exclusions for usage.

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