Skip to main content
Glama
hiyorineko

Rollbar MCP Server

by hiyorineko

rollbar_list_deploys

Retrieve deployment history from Rollbar to track releases, monitor environments, and analyze deployment status for error tracking projects.

Instructions

List deploys from Rollbar

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID
environmentNoEnvironment name
limitNoMaximum number of deploys to return (default: 20)
pageNoPage number for pagination (default: 1)

Implementation Reference

  • Handler for the 'rollbar_list_deploys' tool. Validates project token, resolves effective project ID, constructs API parameters, calls Rollbar API to list deploys, and returns JSON response.
    case "rollbar_list_deploys": {
      // Project Token is required
      if (!projectClient) {
        throw new Error("ROLLBAR_PROJECT_TOKEN is not set, cannot use this API");
      }
    
      const {
        projectId,
        environment,
        limit = 20,
        page = 1,
      } = args as {
        projectId: number;
        environment?: string;
        limit?: number;
        page?: number;
      };
    
      // Use environment variable project ID as default value, or search by project name
      const effectiveProjectId = await getEffectiveProjectId(projectId);
    
      if (!effectiveProjectId) {
        throw new Error("Project ID is required but not provided in request or environment variables");
      }
    
      const params: Record<string, string | number> = { page, limit };
      if (environment) params.environment = environment;
    
      const response = await projectClient.get<ListDeploysResponse>(`/project/${effectiveProjectId}/deploys`, {
        params,
      });
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Schema definition for the 'rollbar_list_deploys' tool, specifying input parameters including required projectId and optional environment, limit, page.
    const LIST_DEPLOYS_TOOL: Tool = {
      name: "rollbar_list_deploys",
      description: "List deploys from Rollbar",
      inputSchema: {
        type: "object",
        properties: {
          projectId: { type: "number", description: "Project ID" },
          environment: { type: "string", description: "Environment name" },
          limit: { type: "number", description: "Maximum number of deploys to return (default: 20)" },
          page: { type: "number", description: "Page number for pagination (default: 1)" },
        },
        required: ["projectId"],
      },
    };
  • src/rollbar.ts:298-314 (registration)
    Registration of the 'rollbar_list_deploys' tool (as LIST_DEPLOYS_TOOL) in the ListTools response handler, making it available to clients.
    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 states 'List deploys from Rollbar', which implies a read-only operation, but does not specify aspects like pagination behavior (implied by 'limit' and 'page' parameters), rate limits, authentication needs, or what the return format looks like. This leaves significant gaps in understanding the tool's behavior.

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 zero waste: 'List deploys from Rollbar'. It is front-loaded and appropriately sized for its purpose, making it easy to scan and understand quickly without unnecessary 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 tool's complexity (4 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits, output format, and usage context. While the schema covers parameters well, the description does not compensate for missing annotations or output schema, leaving users with insufficient information for effective tool invocation.

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 parameter definitions (e.g., 'projectId' as required, 'limit' with default). The description does not add any meaning beyond the schema, such as explaining how parameters interact or providing examples. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List deploys from Rollbar' clearly states the verb ('List') and resource ('deploys from Rollbar'), providing a basic purpose. However, it lacks specificity about scope (e.g., all deploys vs. filtered) and does not distinguish it from sibling tools like 'rollbar_get_deploy', which might retrieve a single deploy. This makes it vague in 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. It does not mention any context, prerequisites, or exclusions, such as how it differs from 'rollbar_get_deploy' for single deploys or 'rollbar_list_items' for other resources. Without such information, users must infer usage from 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