Skip to main content
Glama
BrowserGenie

BrowserGenie MCP Server

by BrowserGenie

monitor_console_events

Monitor console events from a browser tab. Start, stop, or retrieve captured logs filtered by severity level.

Instructions

Real-time console event monitoring. Start monitoring, get events since last read, or stop. Filter by log level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesStart, stop, or get events since last read
levelsNoLog levels to capture
tabIdNoTarget tab ID (defaults to currently active tab)
apiKeyNoAPI key for authentication if enabled

Implementation Reference

  • The handler for 'monitor_console_events' - registers the tool with an async handler that sends a 'monitor_console_events' command via WebSocket bridge, accepting action, levels, tabId, and apiKey parameters.
    server.tool(
      'monitor_console_events',
      'Real-time console event monitoring. Start monitoring, get events since last read, or stop. Filter by log level.',
      {
        action: z.enum(['start', 'stop', 'get']).describe('Start, stop, or get events since last read'),
        levels: z.array(z.enum(['log', 'warn', 'error', 'info'])).optional().default(['error', 'warn']).describe('Log levels to capture'),
        tabId: z.number().optional().describe('Target tab ID (defaults to currently active tab)'),
        apiKey: z.string().optional().describe('API key for authentication if enabled'),
      },
      async ({ action, levels, tabId, apiKey }) => {
        const result = await bridge.sendCommand({
          command: 'monitor_console_events',
          params: { action, levels },
          tabId,
          apiKey,
          timeout: LONG_TIMEOUT,
        });
        if (!result.success) {
          return { content: [{ type: 'text', text: `Error: ${result.error?.message}` }], isError: true };
        }
        return { content: [{ type: 'text', text: JSON.stringify(result.data, null, 2) }] };
      }
    );
  • Input schema for 'monitor_console_events' - defines action (start/stop/get), levels (array of log/warn/error/info, defaults to error+warn), optional tabId, and optional apiKey.
    {
      action: z.enum(['start', 'stop', 'get']).describe('Start, stop, or get events since last read'),
      levels: z.array(z.enum(['log', 'warn', 'error', 'info'])).optional().default(['error', 'warn']).describe('Log levels to capture'),
      tabId: z.number().optional().describe('Target tab ID (defaults to currently active tab)'),
      apiKey: z.string().optional().describe('API key for authentication if enabled'),
    },
  • Registration of the 'monitor_console_events' tool via server.tool() inside registerMonitoringTools().
    server.tool(
      'monitor_console_events',
      'Real-time console event monitoring. Start monitoring, get events since last read, or stop. Filter by log level.',
  • registerMonitoringTools is called from registerAllTools(), which wires up all tools to the server.
    registerMonitoringTools(server, bridge);
  • The WebSocketBridge.sendCommand() method that dispatches the monitor_console_events command to the Chrome extension over WebSocket.
    async sendCommand(cmd: BridgeCommand): Promise<BridgeResponse> {
      if (!this.isConnected()) {
        return {
          success: false,
          error: {
            code: 'NOT_CONNECTED',
            message: 'Chrome extension is not connected. Ensure the extension is installed, enabled, and the browser is running.',
          },
        };
      }
    
      const id = crypto.randomUUID();
      const timeout = cmd.timeout ?? DEFAULT_TIMEOUT;
    
      return new Promise<BridgeResponse>((resolve, reject) => {
        const timer = setTimeout(() => {
          this.pending.delete(id);
          resolve({
            success: false,
            error: {
              code: 'TIMEOUT',
              message: `Command '${cmd.command}' timed out after ${timeout}ms`,
            },
          });
        }, timeout);
    
        this.pending.set(id, { resolve, reject, timer });
    
        const message = {
          id,
          type: 'request',
          command: cmd.command,
          params: cmd.params,
          tabId: cmd.tabId,
          apiKey: cmd.apiKey,
          timestamp: Date.now(),
        };
    
        this.client!.send(JSON.stringify(message));
      });
    }
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions real-time monitoring but omits details like whether starting clears previous events, how long monitoring persists, or if stopping affects the console state. This lack of behavioral context makes it insufficient for an agent to understand side effects.

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 two sentences, front-loaded with the core purpose, and wastes no words. Every sentence adds value.

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 4 parameters and no output schema, the description should cover return value format, behavior for 'get' (e.g., whether it returns only new events since last read), and life cycle of monitoring. It lacks these details, making it incomplete for an agent to use reliably.

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?

With 100% input schema coverage, the description adds little beyond the schema. It reiterates filtering by log level and lists actions, but does not provide extra meaning like format constraints or interaction between parameters (e.g., levels default). Baseline of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool performs real-time console event monitoring with specific actions (start, stop, get) and filtering by log level. This distinguishes it from sibling tools like get_console_logs (which likely retrieves past logs) and assert_no_console_errors (an assertion).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for real-time monitoring but does not explicitly state when to use this tool versus alternatives like get_console_logs or assert_no_console_errors. No exclusions or scenario guidance is provided.

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/BrowserGenie/mcp'

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