Skip to main content
Glama

browser_console_messages

Retrieve console messages from browser sessions to monitor JavaScript errors, warnings, and logs during automated testing or web scraping.

Instructions

Get console

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
levelNo

Implementation Reference

  • index.js:460-466 (registration)
    Registration of the 'browser_console_messages' tool. It uses `proxyToolCall` to delegate the execution.
    server.tool('browser_console_messages', 'Get console', {
      level: z.string().optional()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_console_messages', args);
    });
  • The proxyToolCall function acts as the handler implementation, delegating the tool call to the client instance.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
        log(`[proxyToolCall] Result type: ${typeof result}`);
        log(`[proxyToolCall] Result: ${JSON.stringify(result).slice(0, 500)}`);
    
        // The SDK returns { content: [...], isError?: boolean }

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/OMGEverdo/browser-pool-mcp'

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