Skip to main content
Glama
williamvd4

Playwright Server

by williamvd4

playwright_evaluate

Execute JavaScript code directly in the browser console to automate interactions, extract data, or modify web 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 EvaluateToolHandler class that executes the playwright_evaluate tool by running JavaScript on the page using page.evaluate(script).
    class EvaluateToolHandler(ToolHandler):
        async def handle(self, name: str, arguments: dict | None) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:
            if not self._sessions:
                return [types.TextContent(type="text", text="No active session. Please create a new session first.")]
            session_id = list(self._sessions.keys())[-1]
            page = self._sessions[session_id]["page"]
            script = arguments.get("script")
            result = await page.evaluate(script)
            return [types.TextContent(type="text", text=f"Evaluated script, result: {result}")]
  • JSON Schema definition for the playwright_evaluate tool inputs.
    types.Tool(
        name="playwright_evaluate",
        description="Execute JavaScript in the browser console",
        inputSchema={
            "type": "object",
            "properties": {
                "script": {"type": "string", "description": "JavaScript code to execute"}
            },
            "required": ["script"]
        }
    ),
  • Registration of the EvaluateToolHandler in the tool_handlers dictionary used by the call_tool handler.
    "playwright_evaluate": EvaluateToolHandler(),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Execute JavaScript' implies a mutation operation, it doesn't specify security implications, execution context limitations, error handling, or what happens to the browser state. This is inadequate for a tool that runs arbitrary code in a browser environment.

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, efficient sentence with zero wasted words. It's front-loaded with the core functionality and appropriately sized for a simple tool with one parameter.

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 no annotations and no output schema, the description is insufficient for a tool that executes arbitrary JavaScript in a browser. It lacks critical information about return values, error conditions, security context, and how this differs from other playwright tools, leaving significant gaps for agent understanding.

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 completely. The description doesn't add any additional meaning about parameter usage, constraints, or examples beyond what the schema provides, meeting the baseline for high schema coverage.

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'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like playwright_get_html_content or playwright_get_text_content, which might also involve JavaScript execution indirectly.

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 about when to use this tool versus alternatives. The description doesn't mention scenarios where this is preferred over other playwright tools or when it should be avoided, leaving the agent with no usage context.

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/williamvd4/playwright-plus-python-mcp'

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