Skip to main content
Glama
devskido

Playwright MCP Server

by devskido

playwright_console_logs

Retrieve and filter browser console logs for debugging web applications. Capture errors, warnings, and other console messages with search and limit options.

Instructions

Retrieve console logs from the browser with filtering options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoType of logs to retrieve (all, error, warning, log, info, debug, exception)
searchNoText to search for in logs (handles text with square brackets)
limitNoMaximum number of logs to return
clearNoWhether to clear logs after retrieval (default: false)

Implementation Reference

  • ConsoleLogsTool class containing the handler logic for 'playwright_console_logs'. The 'execute' method filters console logs by type, search term, limit, and optionally clears them.
    export class ConsoleLogsTool extends BrowserToolBase {
      private consoleLogs: string[] = [];
    
      /**
       * Register a console message
       * @param type The type of console message
       * @param text The text content of the message
       */
      registerConsoleMessage(type: string, text: string): void {
        const logEntry = `[${type}] ${text}`;
        this.consoleLogs.push(logEntry);
      }
    
      /**
       * Execute the console logs tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        // No need to use safeExecute here as we don't need to interact with the page
        // We're just filtering and returning logs that are already stored
        
        let logs = [...this.consoleLogs];
        
        // Filter by type if specified
        if (args.type && args.type !== 'all') {
          logs = logs.filter(log => log.startsWith(`[${args.type}]`));
        }
        
        // Filter by search text if specified
        if (args.search) {
          logs = logs.filter(log => log.includes(args.search));
        }
        
        // Limit the number of logs if specified
        if (args.limit && args.limit > 0) {
          logs = logs.slice(-args.limit);
        }
        
        // Clear logs if requested
        if (args.clear) {
          this.consoleLogs = [];
        }
        
        // Format the response
        if (logs.length === 0) {
          return createSuccessResponse("No console logs matching the criteria");
        } else {
          return createSuccessResponse([
            `Retrieved ${logs.length} console log(s):`,
            ...logs
          ]);
        }
      }
    
      /**
       * Get all console logs
       */
      getConsoleLogs(): string[] {
        return this.consoleLogs;
      }
    
      /**
       * Clear all console logs
       */
      clearConsoleLogs(): void {
        this.consoleLogs = [];
      }
    } 
  • Input schema definition for the 'playwright_console_logs' tool in createToolDefinitions().
    {
      name: "playwright_console_logs",
      description: "Retrieve console logs from the browser with filtering options",
      inputSchema: {
        type: "object",
        properties: {
          type: {
            type: "string",
            description: "Type of logs to retrieve (all, error, warning, log, info, debug, exception)",
            enum: ["all", "error", "warning", "log", "info", "debug", "exception"]
          },
          search: {
            type: "string",
            description: "Text to search for in logs (handles text with square brackets)"
          },
          limit: {
            type: "number",
            description: "Maximum number of logs to return"
          },
          clear: {
            type: "boolean",
            description: "Whether to clear logs after retrieval (default: false)"
          }
        },
        required: [],
      },
    },
  • Switch case in handleToolCall that dispatches to ConsoleLogsTool.execute for 'playwright_console_logs'.
    case "playwright_console_logs":
      return await consoleLogsTool.execute(args, context);
  • Instantiation of ConsoleLogsTool instance in initializeTools.
    if (!consoleLogsTool) consoleLogsTool = new ConsoleLogsTool(server);
  • Import of ConsoleLogsTool from './tools/browser/index.js'.
    ConsoleLogsTool,
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 provides minimal behavioral information. It mentions 'filtering options' but doesn't disclose important behaviors like whether this requires an active Playwright session, what format the logs are returned in, if there are rate limits, or what happens when no logs exist. The 'clear' parameter description in the schema hints at side effects, but the main description doesn't highlight this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that gets straight to the point. It's appropriately sized for a tool with good schema coverage. Every word earns its place, though it could be slightly more informative given the lack of annotations.

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 complexity of browser log retrieval (4 parameters, no output schema, no annotations), the description is insufficient. It doesn't explain what format the logs are returned in, whether this requires an active browser context, or what typical use cases are. For a tool with behavioral implications (the 'clear' parameter can modify state), more context is needed.

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 the schema already fully documents all four parameters. The description adds minimal value beyond the schema by mentioning 'filtering options' which aligns with the 'type' and 'search' parameters. No additional semantic context is provided beyond what's in the structured schema descriptions.

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 verb ('retrieve') and resource ('console logs from the browser'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'playwright_get_visible_html' or 'playwright_get_visible_text' which also retrieve browser content but different types.

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. The description mentions 'filtering options' but doesn't specify scenarios where this is preferable over other retrieval tools or when it should be avoided. There's no mention of prerequisites like requiring an active browser session.

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/devskido/customed-playwright'

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