Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_list_users

Retrieve a list of users from Rollbar error tracking to manage team access and permissions for monitoring and debugging applications.

Instructions

List users from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'rollbar_list_users' tool. It verifies the account client is available, makes a GET request to Rollbar's /users endpoint, and returns the response data as formatted JSON.
    case "rollbar_list_users": {
      // Account Token is required
      if (!accountClient) {
        throw new Error("ROLLBAR_ACCOUNT_TOKEN is not set, cannot use this API");
      }
    
      const response = await accountClient.get<ListUsersResponse>("/users");
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Input schema and metadata definition for the 'rollbar_list_users' tool, specifying no input parameters are required.
    const LIST_USERS_TOOL: Tool = {
      name: "rollbar_list_users",
      description: "List users from Rollbar",
      inputSchema: {
        type: "object",
        properties: {},
      },
    };
  • src/rollbar.ts:299-313 (registration)
    Registration of the 'rollbar_list_users' tool (as LIST_USERS_TOOL) in the listToolsRequestSchema handler, making it discoverable by MCP clients.
    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,
    ],
  • TypeScript interface defining the expected response structure for the Rollbar users list API.
    export interface ListUsersResponse {
      users: RollbarUser[];
    }
  • TypeScript interface defining the structure of a Rollbar user object used in responses.
    export interface RollbarUser {
      id: number;
      username: string;
      email: string;
      access_level: number;
    }
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 users from Rollbar' implies a read operation, but it doesn't disclose any behavioral traits like pagination behavior, rate limits, authentication requirements, error conditions, or what format the user data will be returned in. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool actually 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 extremely concise - just four words that directly state the tool's purpose. There's zero waste or unnecessary elaboration. It's front-loaded with the essential information and doesn't bury the key purpose in verbose text.

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 that there are no annotations, no output schema, and the description provides only basic purpose information, this is incomplete for effective tool use. The agent knows what the tool does but not how it behaves, what it returns, when to use it versus alternatives, or any operational constraints. For even a simple list operation, more context would be helpful for an AI agent.

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 there are no parameters to describe). The description doesn't need to add parameter semantics since there are no parameters. The baseline for zero parameters is 4, as there's nothing for the description to compensate for regarding 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 ('users from Rollbar'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'rollbar_get_user', which appears to retrieve a single user rather than list multiple users. The description is specific about what it does but lacks sibling differentiation.

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. There's no mention of when to use 'rollbar_list_users' versus 'rollbar_get_user', nor any context about prerequisites, permissions, or typical use cases. The agent receives no usage instructions beyond the basic purpose statement.

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