Skip to main content
Glama
jomon003

PlayMCP Browser Automation Server

by jomon003

evaluateWithReturn

Execute JavaScript code in a browser automation context and retrieve the returned result for web scraping, testing, or interaction tasks.

Instructions

Execute JavaScript code and return the result

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptYesJavaScript code to execute

Implementation Reference

  • The core handler function that executes the provided JavaScript script on the current page using page.evaluate() and returns the result.
    async evaluateWithReturn(script: string): Promise<any> {
      try {
        if (!this.isInitialized() || !this.state.page) {
          throw new Error('Browser not initialized');
        }
        this.log('Evaluating JavaScript with return', { script });
        const result = await this.state.page.evaluate(script);
        this.log('JavaScript evaluation complete');
        return result;
      } catch (error: any) {
        console.error('JavaScript evaluation error:', error);
        throw new BrowserError('Failed to evaluate JavaScript', 'Check if the script is valid JavaScript');
      }
    }
  • Tool schema definition including input schema that requires a 'script' string parameter.
    const EVALUATE_WITH_RETURN_TOOL: Tool = {
      name: "evaluateWithReturn",
      description: "Execute JavaScript code and return the result",
      inputSchema: {
        type: "object",
        properties: {
          script: { 
            type: "string",
            description: "JavaScript code to execute"
          }
        },
        required: ["script"]
      }
    };
  • src/server.ts:514-553 (registration)
    Registration of the tool in the tools object passed to MCP server capabilities.
    const tools = {
      openBrowser: OPEN_BROWSER_TOOL,
      navigate: NAVIGATE_TOOL,
      type: TYPE_TOOL,
      click: CLICK_TOOL,
      moveMouse: MOVE_MOUSE_TOOL,
      scroll: SCROLL_TOOL,
      screenshot: SCREENSHOT_TOOL,
      getPageSource: GET_PAGE_SOURCE_TOOL,
      getPageText: GET_PAGE_TEXT_TOOL,
      getPageTitle: GET_PAGE_TITLE_TOOL,
      getPageUrl: GET_PAGE_URL_TOOL,
      getScripts: GET_SCRIPTS_TOOL,
      getStylesheets: GET_STYLESHEETS_TOOL,
      getMetaTags: GET_META_TAGS_TOOL,
      getLinks: GET_LINKS_TOOL,
      getImages: GET_IMAGES_TOOL,
      getForms: GET_FORMS_TOOL,
      getElementContent: GET_ELEMENT_CONTENT_TOOL,
      getElementHierarchy: GET_ELEMENT_HIERARCHY_TOOL,
      executeJavaScript: EXECUTE_JAVASCRIPT_TOOL,
      goForward: GO_FORWARD_TOOL,
      hover: HOVER_TOOL,
      dragAndDrop: DRAG_AND_DROP_TOOL,
      selectOption: SELECT_OPTION_TOOL,
      pressKey: PRESS_KEY_TOOL,
      waitForText: WAIT_FOR_TEXT_TOOL,
      waitForSelector: WAIT_FOR_SELECTOR_TOOL,
      resize: RESIZE_TOOL,
      handleDialog: HANDLE_DIALOG_TOOL,
      getConsoleMessages: GET_CONSOLE_MESSAGES_TOOL,
      getNetworkRequests: GET_NETWORK_REQUESTS_TOOL,
      uploadFiles: UPLOAD_FILES_TOOL,
      evaluateWithReturn: EVALUATE_WITH_RETURN_TOOL,
      takeScreenshot: TAKE_SCREENSHOT_TOOL,
      mouseMove: MOUSE_MOVE_TOOL,
      mouseClick: MOUSE_CLICK_TOOL,
      mouseDrag: MOUSE_DRAG_TOOL,
      closeBrowser: CLOSE_BROWSER_TOOL
    };
  • src/server.ts:926-940 (registration)
    MCP callTool request handler case that validates input and delegates to the playwright controller's evaluateWithReturn method.
    case 'evaluateWithReturn': {
      if (!args.script || typeof args.script !== 'string') {
        return {
          content: [{ type: "text", text: "JavaScript script is required" }],
          isError: true
        };
      }
      const result = await playwrightController.evaluateWithReturn(args.script);
      return {
        content: [{ 
          type: "text", 
          text: result !== undefined ? JSON.stringify(result, null, 2) : "null"
        }]
      };
    }
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 it states the basic action and outcome, it lacks critical details such as execution context (e.g., browser environment, sandboxing), error handling, security implications, or performance characteristics that would be essential for safe and effective use.

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 six words, front-loading the core functionality with zero wasted language. Every word earns its place by directly contributing to understanding the tool's purpose.

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 arbitrary JavaScript code (which carries security and reliability risks), the absence of annotations, no output schema, and minimal description, this is inadequate. The description doesn't address execution environment, return value format, error conditions, or safety considerations needed for complete 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?

The schema description coverage is 100%, with the single parameter 'script' clearly documented as 'JavaScript code to execute'. The description adds no additional semantic context beyond what the schema provides, such as examples of valid code or constraints, 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 code') and outcome ('return the result'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'executeJavaScript', which appears to serve a similar purpose based on naming, leaving some ambiguity about differentiation.

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 'executeJavaScript' or other JavaScript-related tools in the sibling list. There's no mention of prerequisites, context, or specific use cases that would help an agent choose appropriately.

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/jomon003/PlayMCP'

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