Skip to main content
Glama

getConsoleErrors

Capture and analyze browser console errors to identify JavaScript issues and debugging needs for web applications.

Instructions

Check our browsers console errors

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler and registration for the 'getConsoleErrors' MCP tool. Fetches console errors from the discovered browser connector server via HTTP and returns formatted JSON response.
      "getConsoleErrors",
      "Check our browsers console errors",
      async () => {
        return await withServerConnection(async () => {
          const response = await fetch(
            `http://${discoveredHost}:${discoveredPort}/console-errors`
          );
          const json = await response.json();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(json, null, 2),
              },
            ],
          };
        });
      }
    );
  • Helper function used by getConsoleErrors (and other tools) to ensure connection to the browser server before making API calls, with automatic discovery and reconnection logic.
    async function withServerConnection<T>(
      apiCall: () => Promise<T>
    ): Promise<T | any> {
      // Attempt to discover server if not already discovered
      if (!serverDiscovered) {
        const discovered = await discoverServer();
        if (!discovered) {
          return {
            content: [
              {
                type: "text",
                text: "Failed to discover browser connector server. Please ensure it's running.",
              },
            ],
            isError: true,
          };
        }
      }
    
      // Now make the actual API call with discovered host/port
      try {
        return await apiCall();
      } catch (error: any) {
        // If the request fails, try rediscovering the server once
        console.error(
          `API call failed: ${error.message}. Attempting rediscovery...`
        );
        serverDiscovered = false;
    
        if (await discoverServer()) {
          console.error("Rediscovery successful. Retrying API call...");
          try {
            // Retry the API call with the newly discovered connection
            return await apiCall();
          } catch (retryError: any) {
            console.error(`Retry failed: ${retryError.message}`);
            return {
              content: [
                {
                  type: "text",
                  text: `Error after reconnection attempt: ${retryError.message}`,
                },
              ],
              isError: true,
            };
          }
        } else {
          console.error("Rediscovery failed. Could not reconnect to server.");
          return {
            content: [
              {
                type: "text",
                text: `Failed to reconnect to server: ${error.message}`,
              },
            ],
            isError: true,
          };
        }
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation ('Check') but doesn't disclose whether it requires specific permissions, how errors are retrieved (e.g., real-time vs. stored), or what the output format might be. More context on behavior is needed.

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 no wasted words. It is front-loaded and directly states the tool's purpose without unnecessary elaboration, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what 'Check' entails operationally (e.g., returns a list, triggers a scan), the scope (e.g., current page, all tabs), or error format, leaving gaps for an AI agent to infer behavior.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, and it correctly implies no inputs are required, aligning with the schema.

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 ('Check') and target resource ('browsers console errors'), making the purpose understandable. It distinguishes from some siblings like 'getNetworkErrors' by specifying console errors, but doesn't explicitly differentiate from 'getConsoleLogs' which might overlap.

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?

No guidance is provided on when to use this tool versus alternatives like 'getConsoleLogs' or 'getNetworkErrors'. The description only states what it does without context about appropriate use cases or prerequisites.

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/Sugatraj/Cursor-Browser-Tools-MCP'

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