Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_list_projects

Retrieve all projects from Rollbar error tracking to monitor and manage application health across your development environment.

Instructions

List projects from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler that executes the rollbar_list_projects tool by calling the Rollbar account API to list projects and returns the JSON response.
    case "rollbar_list_projects": {
      // Account Token is required
      if (!accountClient) {
        throw new Error("ROLLBAR_ACCOUNT_TOKEN is not set, cannot use this API");
      }
    
      const response = await accountClient.get<ListProjectsResponse>("/projects");
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • The Tool definition including name, description, and empty input schema for rollbar_list_projects.
    const LIST_PROJECTS_TOOL: Tool = {
      name: "rollbar_list_projects",
      description: "List projects from Rollbar",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/rollbar.ts:298-314 (registration)
    The ListToolsRequestHandler that registers the rollbar_list_projects tool (via LIST_PROJECTS_TOOL) by including it in the list of available tools.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
        LIST_ITEMS_TOOL,
        GET_ITEM_TOOL,
        GET_ITEM_BY_UUID_TOOL,
        GET_ITEM_BY_COUNTER_TOOL,
        LIST_OCCURRENCES_TOOL,
        GET_OCCURRENCE_TOOL,
        LIST_PROJECTS_TOOL,
        GET_PROJECT_TOOL,
        LIST_ENVIRONMENTS_TOOL,
        LIST_USERS_TOOL,
        GET_USER_TOOL,
        LIST_DEPLOYS_TOOL,
        GET_DEPLOY_TOOL,
      ],
    }));
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. 'List projects' implies a read-only operation, but it doesn't specify whether this requires authentication, returns paginated results, includes all projects or filtered subsets, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 states exactly what the tool does with zero wasted words. It's appropriately sized for a simple list operation and is perfectly front-loaded with the core functionality.

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 parameterless list tool with no output schema, the description provides the basic purpose but lacks important context about what the list contains (all projects? filtered?), return format, authentication requirements, or rate limits. Without annotations or output schema, the description should do more to compensate, but it only meets minimum viability.

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% (empty schema is fully described). The description doesn't need to explain any parameters, so it meets the baseline expectation for parameterless tools. No additional parameter information is required or expected.

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 action ('List') and resource ('projects from Rollbar'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'rollbar_get_project' or other list tools like 'rollbar_list_items', which would require more specific scope information to earn a perfect 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 'rollbar_get_project' (for single project details) or other list tools for different resources. There's no mention of prerequisites, context, or comparison with sibling tools, leaving the agent with minimal usage direction.

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/hiyorineko/mcp-rollbar-server'

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