Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_list_items

Retrieve and filter error tracking data from Rollbar to monitor application issues by status, severity level, or environment.

Instructions

List items (errors) from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by status (active, resolved, muted, etc.)
levelNoFilter by level (critical, error, warning, info, debug)
environmentNoFilter by environment (production, staging, etc.)
limitNoMaximum number of items to return (default: 20)
pageNoPage number for pagination (default: 1)

Implementation Reference

  • Executes the rollbar_list_items tool by calling the Rollbar /items API with optional filters for status, level, environment, limit, and page, returning the JSON response.
    case "rollbar_list_items": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const {
        status,
        level,
        environment,
        limit = 20,
        page = 1,
      } = args as {
        status?: string;
        level?: string;
        environment?: string;
        limit?: number;
        page?: number;
      };
    
      const params: Record<string, string | number> = { page, limit };
      if (status) params.status = status;
      if (level) params.level = level;
      if (environment) params.environment = environment;
    
      const response = await projectClient.get<ListItemsResponse>("/items", { params });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Defines the input schema, name, and description for the rollbar_list_items tool.
    const LIST_ITEMS_TOOL: Tool = {
      name: "rollbar_list_items",
      description: "List items (errors) from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          status: { type: "string", description: "Filter by status (active, resolved, muted, etc.)" },
          level: { type: "string", description: "Filter by level (critical, error, warning, info, debug)" },
          environment: { type: "string", description: "Filter by environment (production, staging, etc.)" },
          limit: { type: "number", description: "Maximum number of items to return (default: 20)" },
          page: { type: "number", description: "Page number for pagination (default: 1)" },
        },
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registers the rollbar_list_items tool (as LIST_ITEMS_TOOL) in the server's 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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it lists items, without mentioning whether this is a read-only operation, if it requires authentication, any rate limits, pagination behavior beyond the parameters, or what the output format looks like. For a tool with 5 parameters and no output schema, this is a significant gap 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—a single, clear sentence that gets straight to the point without any fluff. It's front-loaded with the core purpose, making it efficient for quick comprehension, though this brevity comes at the cost of missing contextual details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of a listing tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain the return format, pagination behavior beyond parameters, or how to interpret results, leaving critical gaps for an agent to use the tool effectively in context with its siblings.

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, with clear explanations for all 5 parameters (status, level, environment, limit, page). The description adds no additional parameter information beyond what's in the schema, so it meets the baseline of 3 for adequate coverage but doesn't enhance understanding of parameter usage or constraints.

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 ('items (errors) from Rollbar'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'rollbar_list_occurrences' or 'rollbar_list_deploys' beyond specifying 'items (errors)', which provides some distinction but could be more explicit about what makes this listing unique compared to other list tools.

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. With multiple sibling list tools available (e.g., rollbar_list_occurrences, rollbar_list_deploys), there's no indication of what specific scenarios or data types this tool is intended for, leaving the agent to guess based on the name alone.

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