Skip to main content
Glama

playwright_evaluate

Execute JavaScript code directly in the browser console to automate web interactions, extract data, or manipulate page elements during browser automation sessions.

Instructions

Execute JavaScript in the browser console

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptYesJavaScript code to execute

Implementation Reference

  • The EvaluateTool class implements the core logic for the playwright_evaluate tool by executing the provided JavaScript script on the browser page using page.evaluate and returning the result.
    export class EvaluateTool extends BrowserToolBase {
      /**
       * Execute the evaluate tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          const result = await page.evaluate(args.script);
    
          // Convert result to string for display
          let resultStr: string;
          try {
            resultStr = JSON.stringify(result, null, 2);
          } catch (_error) {
            resultStr = String(result);
          }
    
          return createSuccessResponse([`Executed JavaScript:`, `${args.script}`, `Result:`, `${resultStr}`]);
        });
      }
    }
  • Schema definition for the playwright_evaluate tool, specifying the input parameters.
      name: "playwright_evaluate",
      description: "Execute JavaScript in the browser console",
      inputSchema: {
        type: "object",
        properties: {
          script: { type: "string", description: "JavaScript code to execute" },
        },
        required: ["script"],
      },
    },
  • Tool registration in the main handleToolCall switch statement, which dispatches calls to the EvaluateTool instance.
    case "playwright_evaluate":
      return await evaluateTool.execute(args, context);
  • Instantiation of the EvaluateTool instance during tool initialization.
    if (!evaluateTool) evaluateTool = new EvaluateTool(server);
  • Inclusion in BROWSER_TOOLS array used to determine browser requirements.
    "playwright_evaluate",
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 only states what the tool does without behavioral details. It doesn't disclose execution context (e.g., current page, frame), error handling, security implications, or what happens with the JavaScript return value. For a JavaScript execution tool with zero annotation coverage, this is insufficient.

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 extremely concise at just 5 words, front-loading the core functionality with zero wasted words. Every element ('Execute', 'JavaScript', 'in the browser console') contributes essential information.

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?

For a JavaScript execution tool with no annotations and no output schema, the description is incomplete. It doesn't explain what gets returned, error conditions, execution scope, or security considerations. Given the complexity of browser JavaScript execution, more context is needed for safe and effective use.

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 documents the single 'script' parameter. The description doesn't add any additional semantic context about the JavaScript execution environment, supported APIs, or return value handling beyond what the schema provides.

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 ('Execute JavaScript') and location ('in the browser console'), which distinguishes it from other browser automation tools. However, it doesn't explicitly differentiate from potential sibling tools that might also execute JavaScript in different contexts.

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?

The description provides no guidance on when to use this tool versus alternatives like other Playwright tools for browser interaction. There's no mention of prerequisites, typical use cases, or limitations compared to similar tools.

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

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