Skip to main content
Glama
BrowserGenie

BrowserGenie MCP Server

by BrowserGenie

get_all_issues

Collects console errors, network failures, and broken resources in one request to quickly assess page health.

Instructions

Unified diagnostic tool that returns console errors, network errors, and broken resources in a single call. Use this for a quick health check. For deeper inspection of a specific category, use get_console_logs, get_network_errors, or audit_broken_resources individually. Note: resource inspection requires the CDP debugger to be attached. If Chrome DevTools is open on the tab, resource inspection may be skipped but console/network data will still be returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
includeConsoleNoInclude console errors and warnings
includeNetworkNoInclude failed network requests
includeResourcesNoInclude broken images, stylesheets, and fonts
clearAfterNoClear logs after retrieval
tabIdNoTarget tab ID (defaults to currently active tab)
apiKeyNoAPI key for authentication if enabled

Implementation Reference

  • The handler function that executes the 'get_all_issues' tool logic. It accepts optional parameters (includeConsole, includeNetwork, includeResources, clearAfter, tabId, apiKey), sends a bridge command via WebSocket to the extension, and returns the result (console errors, network errors, and broken resources) as formatted JSON.
    server.tool(
      'get_all_issues',
      'Unified diagnostic tool that returns console errors, network errors, and broken resources in a single call. Use this for a quick health check. For deeper inspection of a specific category, use get_console_logs, get_network_errors, or audit_broken_resources individually. Note: resource inspection requires the CDP debugger to be attached. If Chrome DevTools is open on the tab, resource inspection may be skipped but console/network data will still be returned.',
      {
        includeConsole: z.boolean().optional().default(true).describe('Include console errors and warnings'),
        includeNetwork: z.boolean().optional().default(true).describe('Include failed network requests'),
        includeResources: z.boolean().optional().default(true).describe('Include broken images, stylesheets, and fonts'),
        clearAfter: z.boolean().optional().default(false).describe('Clear logs after retrieval'),
        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 ({ includeConsole, includeNetwork, includeResources, clearAfter, tabId, apiKey }) => {
        const result = await bridge.sendCommand({
          command: 'get_all_issues',
          params: { includeConsole, includeNetwork, includeResources, clearAfter },
          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) }] };
      }
    );
  • Zod schema defining the input parameters for the tool: includeConsole, includeNetwork, includeResources (all booleans with default true), clearAfter (boolean, default false), tabId (optional number), apiKey (optional string).
    {
      includeConsole: z.boolean().optional().default(true).describe('Include console errors and warnings'),
      includeNetwork: z.boolean().optional().default(true).describe('Include failed network requests'),
      includeResources: z.boolean().optional().default(true).describe('Include broken images, stylesheets, and fonts'),
      clearAfter: z.boolean().optional().default(false).describe('Clear logs after retrieval'),
      tabId: z.number().optional().describe('Target tab ID (defaults to currently active tab)'),
      apiKey: z.string().optional().describe('API key for authentication if enabled'),
    },
  • The tool is registered via the registerQaTools function call in src/tools/index.ts, which is called during server setup to register all QA-related tools including 'get_all_issues'.
      registerQaTools(server, bridge);
      registerGestureTools(server, bridge);
      registerMacroTools(server, bridge);
      registerVisualRegressionTools(server, bridge);
    }
  • The LONG_TIMEOUT constant (60 seconds) is used as the timeout for the bridge.sendCommand call within the tool handler.
    export const LONG_TIMEOUT = 60_000;
    export const WEBSOCKET_PORT = parseInt(process.env.WEBSOCKET_PORT || '7890', 10);
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that resource inspection requires CDP debugger and may be skipped if Chrome DevTools is open. However, it does not mention the destructive potential of the 'clearAfter' parameter.

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?

Three sentences, each adding value: purpose, use case, and behavioral detail. Front-loaded and no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers overall purpose and key behavioral nuance (CDP requirement). Missing mention of return value format and the clearAfter effect, but sufficient for a quick health check tool.

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?

Schema description coverage is 100%, so baseline is 3. The description adds context about the categories and CDP condition, but does not significantly enhance understanding of individual parameters beyond what the schema already provides.

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 it is a unified diagnostic tool returning console errors, network errors, and broken resources. It distinguishes from sibling tools by naming alternatives for deeper inspection.

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

Usage Guidelines5/5

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

Explicitly says 'Use this for a quick health check' and provides when-not-to-use: for deeper inspection of a specific category, use the individual tools. This gives clear guidance.

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