Skip to main content
Glama

execute-code

Execute custom JavaScript code using Playwright to interact with web pages, retrieve page data, and perform automated browser actions for testing and automation workflows.

Instructions

Execute custom Playwright JS code against the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesThe Playwright code to execute. Must be an async function declaration that takes a page parameter. Example: async function run(page) { console.log(await page.title()); return await page.title(); } Returns an object with: - result: The return value from your function - logs: Array of console logs from execution - errors: Array of any errors encountered Example response: {"result": "Google", "logs": ["[log] Google"], "errors": []}

Implementation Reference

  • Registration of the 'execute-code' MCP tool, including input schema, description, and handler function that logs usage and delegates execution to secureEvalAsync helper.
    server.tool(
      'execute-code',
      'Execute custom Playwright JS code against the current page',
      {
        code: z.string().describe(`The Playwright code to execute. Must be an async function declaration that takes a page parameter.
    
    Example:
    async function run(page) {
      console.log(await page.title());
      return await page.title();
    }
    
    Returns an object with:
    - result: The return value from your function
    - logs: Array of console logs from execution
    - errors: Array of any errors encountered
    
    Example response:
    {"result": "Google", "logs": ["[log] Google"], "errors": []}`)
      },
      async ({ code }) => {
        posthogServer.capture({
          distinctId: getUserId(),
          event: 'execute_code',
          properties: {
            codeLength: code.length,
          },
        });
    
        const result = await secureEvalAsync(page, code);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2) // Pretty print the JSON
            }
          ]
        };
      }
    )
  • The MCP tool handler function for 'execute-code'. Captures analytics, executes the code via secureEvalAsync, and returns the result as pretty-printed JSON text content.
      async ({ code }) => {
        posthogServer.capture({
          distinctId: getUserId(),
          event: 'execute_code',
          properties: {
            codeLength: code.length,
          },
        });
    
        const result = await secureEvalAsync(page, code);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(result, null, 2) // Pretty print the JSON
            }
          ]
        };
      }
    )
  • Input schema for the 'execute-code' tool using Zod, defining the 'code' string parameter with detailed usage instructions and examples.
      {
        code: z.string().describe(`The Playwright code to execute. Must be an async function declaration that takes a page parameter.
    
    Example:
    async function run(page) {
      console.log(await page.title());
      return await page.title();
    }
    
    Returns an object with:
    - result: The return value from your function
    - logs: Array of console logs from execution
    - errors: Array of any errors encountered
    
    Example response:
    {"result": "Google", "logs": ["[log] Google"], "errors": []}`)
      },
  • Supporting utility function that securely executes the provided async Playwright code in a Node.js vm sandbox. Injects the page object, overrides console to capture logs/errors, wraps code to call run(page), and returns structured result with result/logs/errors.
    export const secureEvalAsync = async (page: Page, code: string, context = {}) => {
      // Set default options
      const timeout = 20000;
      const filename = 'eval.js';
    
      let logs: string[] = [];
      let errors: string[] = [];
    
      // Code should already be a function declaration
      // Just need to execute it with page argument
      const wrappedCode = `
        ${code}
        run(page);
      `;
    
      // Create restricted sandbox with provided context
      const sandbox = {
        // Core async essentials
        Promise,
        setTimeout,
        clearTimeout,
        setImmediate,
        clearImmediate,
    
        // Pass page object to sandbox
        page,
    
        // Capture all console methods
        console: {
          log: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            logs.push(`[log] ${msg}`);
          },
          error: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            errors.push(`[error] ${msg}`);
          },
          warn: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            logs.push(`[warn] ${msg}`);
          },
          info: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            logs.push(`[info] ${msg}`);
          },
          debug: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            logs.push(`[debug] ${msg}`);
          },
          trace: (...args: any[]) => {
            const msg = args.map(arg => String(arg)).join(' ');
            logs.push(`[trace] ${msg}`);
          }
        },
    
        // User-provided context
        ...context,
    
        // Explicitly block access to sensitive globals
        process: undefined,
        global: undefined,
        require: undefined,
        __dirname: undefined,
        __filename: undefined,
        Buffer: undefined
      };
    
      try {
        // Create context and script
        const vmContext = vm.createContext(sandbox);
        const script = new vm.Script(wrappedCode, { filename });
    
        // Execute and await result
        const result = script.runInContext(vmContext);
        const awaitedResult = await result;
    
        return {
          result: awaitedResult,
          logs,
          errors
        };
    
      } catch (error: any) {
        return {
          error: true,
          message: error.message,
          stack: error.stack,
          logs,
          errors
        };
      }
    }
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it executes code asynchronously, requires a specific function structure (async with page parameter), and details the return format (result, logs, errors). It doesn't mention rate limits, auth needs, or destructive effects, but covers execution mechanics adequately for a tool with no annotations.

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, front-loaded sentence that directly states the tool's purpose with zero waste. Every word earns its place by specifying the action, code type, and target, making it highly efficient and easy to parse.

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?

Given one parameter with full schema coverage and no output schema, the description is reasonably complete. It explains the execution process and return format, compensating for the lack of output schema. However, it doesn't address potential errors or side effects beyond the listed response fields, leaving minor gaps for a code execution tool.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds value by emphasizing the code must be 'Playwright JS' and executed 'against the current page', providing context beyond the schema's technical details. It doesn't elaborate on parameter syntax beyond the example, but enhances understanding of the tool's scope.

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 ('execute') and resource ('custom Playwright JS code') with the target ('against the current page'). It distinguishes from siblings like get-context or get-screenshot by focusing on code execution rather than retrieval or capture. However, it doesn't explicitly differentiate from init-browser in terms of browser lifecycle management.

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

Usage Guidelines3/5

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

The description implies usage for executing custom code on a page, suggesting it's for dynamic interactions beyond simple data fetching. No explicit guidance on when to use vs. alternatives like get-full-dom for static content or prerequisites (e.g., requires an initialized browser). The context is clear but lacks specific exclusions or named alternatives.

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/Ashish-Bansal/playwright-mcp'

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