Skip to main content
Glama
cploujoux

Puppeteer MCP Server

by cploujoux

puppeteer_evaluate

Execute JavaScript in a browser console to automate interactions, extract data, or manipulate web pages using Puppeteer MCP Server.

Instructions

Execute JavaScript in the browser console

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptYesJavaScript code to execute

Implementation Reference

  • Handler for puppeteer_evaluate tool: executes the provided JavaScript script in the browser page context, overrides console methods to capture logs, returns execution result and console output.
    case "puppeteer_evaluate":
      try {
        await page.evaluate(() => {
          window.mcpHelper = {
            logs: [],
            originalConsole: { ...console },
          };
    
          ["log", "info", "warn", "error"].forEach((method) => {
            (console as any)[method] = (...args: any[]) => {
              window.mcpHelper.logs.push(`[${method}] ${args.join(" ")}`);
              (window.mcpHelper.originalConsole as any)[method](...args);
            };
          });
        });
    
        const result = await page.evaluate(args.script);
    
        const logs = await page.evaluate(() => {
          Object.assign(console, window.mcpHelper.originalConsole);
          const logs = window.mcpHelper.logs;
          delete (window as any).mcpHelper;
          return logs;
        });
    
        return {
          content: [
            {
              type: "text",
              text: `Execution result:\n${JSON.stringify(
                result,
                null,
                2
              )}\n\nConsole output:\n${logs.join("\n")}`,
            },
          ],
          isError: false,
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Script execution failed: ${(error as Error).message}`,
            },
          ],
          isError: true,
        };
      }
  • Schema definition for puppeteer_evaluate tool, specifying input as a JavaScript script string.
    {
      name: "puppeteer_evaluate",
      description: "Execute JavaScript in the browser console",
      inputSchema: {
        type: "object",
        properties: {
          script: { type: "string", description: "JavaScript code to execute" },
        },
        required: ["script"],
      },
    },
  • index.ts:18-122 (registration)
    Registration of puppeteer_evaluate in the TOOLS array used for listing available tools.
    const TOOLS: Tool[] = [
      {
        name: "puppeteer_navigate",
        description: "Navigate to a URL",
        inputSchema: {
          type: "object",
          properties: {
            url: { type: "string" },
          },
          required: ["url"],
        },
      },
      {
        name: "puppeteer_screenshot",
        description: "Take a screenshot of the current page or a specific element",
        inputSchema: {
          type: "object",
          properties: {
            name: { type: "string", description: "Name for the screenshot" },
            selector: {
              type: "string",
              description: "CSS selector for element to screenshot",
            },
            width: {
              type: "number",
              description: "Width in pixels (default: 800)",
            },
            height: {
              type: "number",
              description: "Height in pixels (default: 600)",
            },
          },
          required: ["name"],
        },
      },
      {
        name: "puppeteer_click",
        description: "Click an element on the page",
        inputSchema: {
          type: "object",
          properties: {
            selector: {
              type: "string",
              description: "CSS selector for element to click",
            },
          },
          required: ["selector"],
        },
      },
      {
        name: "puppeteer_fill",
        description: "Fill out an input field",
        inputSchema: {
          type: "object",
          properties: {
            selector: {
              type: "string",
              description: "CSS selector for input field",
            },
            value: { type: "string", description: "Value to fill" },
          },
          required: ["selector", "value"],
        },
      },
      {
        name: "puppeteer_select",
        description: "Select an element on the page with Select tag",
        inputSchema: {
          type: "object",
          properties: {
            selector: {
              type: "string",
              description: "CSS selector for element to select",
            },
            value: { type: "string", description: "Value to select" },
          },
          required: ["selector", "value"],
        },
      },
      {
        name: "puppeteer_hover",
        description: "Hover an element on the page",
        inputSchema: {
          type: "object",
          properties: {
            selector: {
              type: "string",
              description: "CSS selector for element to hover",
            },
          },
          required: ["selector"],
        },
      },
      {
        name: "puppeteer_evaluate",
        description: "Execute JavaScript in the browser console",
        inputSchema: {
          type: "object",
          properties: {
            script: { type: "string", description: "JavaScript code to execute" },
          },
          required: ["script"],
        },
      },
    ];
  • index.ts:463-465 (registration)
    Registration of the call tool handler which dispatches to puppeteer_evaluate case based on name.
    server.setRequestHandler(CallToolRequestSchema, async (request) =>
      handleToolCall(request.params.name, request.params.arguments ?? {})
    );
  • index.ts:459-461 (registration)
    Registration of list tools handler which includes puppeteer_evaluate from TOOLS.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states what the tool does but lacks behavioral details: it doesn't disclose that this executes in a browser context (implying potential side effects), doesn't mention error handling, return values, or that it might require a page to be loaded. For a tool that executes arbitrary code with no safety annotations, this is a significant gap.

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, clear sentence with zero waste. It's front-loaded with the core purpose and appropriately sized for a simple tool, making it easy for an agent 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 complexity of executing JavaScript in a browser (a potentially powerful/destructive operation), no annotations, no output schema, and 100% schema coverage, the description is incomplete. It doesn't address return values, error cases, or safety considerations, leaving the agent under-informed about behavioral outcomes.

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%, with the single parameter 'script' documented as 'JavaScript code to execute'. The description adds no additional meaning beyond this, such as examples, constraints, or context about the execution environment. With high schema coverage, the baseline is 3, as the schema does the heavy lifting.

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 'Execute JavaScript in the browser console' clearly states the action (execute) and target (JavaScript in browser console). It distinguishes from siblings like click, fill, or navigate by specifying code execution rather than UI interaction or navigation. However, it doesn't explicitly contrast with potential similar tools beyond the provided sibling list.

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 doesn't mention prerequisites (e.g., requires an active browser page), exclusions (e.g., not for DOM manipulation vs. puppeteer_click), or context for choosing between executing JavaScript and using other puppeteer tools. This leaves the agent without usage direction.

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

Related 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/cploujoux/mcp-puppeteer'

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