Skip to main content
Glama
jomon003

PlayMCP Browser Automation Server

by jomon003

mouseMove

Move the mouse cursor to specified screen coordinates for browser automation tasks like clicking elements or navigating interfaces.

Instructions

Move mouse to specific coordinates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYes
yYes

Implementation Reference

  • The main handler function in PlaywrightController that moves the mouse to the specified coordinates using Playwright's page.mouse.move().
    async mouseMove(x: number, y: number): Promise<void> {
      try {
        if (!this.isInitialized() || !this.state.page) {
          throw new Error('Browser not initialized');
        }
        this.log('Moving mouse', { x, y });
        await this.state.page.mouse.move(x, y);
        this.currentMousePosition = { x, y };
        this.log('Mouse move complete');
      } catch (error: any) {
        console.error('Mouse move error:', error);
        throw new BrowserError('Failed to move mouse', 'Check if coordinates are valid');
      }
    }
  • Defines the Tool object for mouseMove, including its input schema validating x and y as required numbers.
    const MOUSE_MOVE_TOOL: Tool = {
      name: "mouseMove",
      description: "Move mouse to specific coordinates",
      inputSchema: {
        type: "object",
        properties: {
          x: { type: "number" },
          y: { type: "number" }
        },
        required: ["x", "y"]
      }
    };
  • src/server.ts:555-565 (registration)
    Registers the tools object (which includes mouseMove) with the MCP Server instance via capabilities.
    const server = new Server(
      {
        name: "playmcp-browser",
        version: "1.0.0",
      },
      {
        capabilities: {
          tools,
        },
      }
    );
  • src/server.ts:514-553 (registration)
    Includes the mouseMove tool in the tools object used for MCP server registration. Note: excerpt abbreviated for brevity.
    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
    };
  • The dispatch logic in the callTool request handler that validates inputs and calls the controller's mouseMove method.
    case 'mouseMove': {
      if (typeof args.x !== 'number' || typeof args.y !== 'number') {
        return {
          content: [{ type: "text", text: "X and Y coordinates are required" }],
          isError: true
        };
      }
      await playwrightController.mouseMove(args.x, args.y);
      return {
        content: [{ type: "text", text: "Mouse moved successfully" }]
      };
    }
Behavior1/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It doesn't disclose if this requires a browser session, has side effects (e.g., triggering hover events), or details execution context. For a tool that likely interacts with UI automation, this lack of transparency is inadequate.

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 with a single, direct sentence that front-loads the core action. There is no wasted verbiage, making it easy to parse quickly, though this brevity contributes to gaps in other dimensions.

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 tool's likely complexity in browser automation, no annotations, no output schema, and low parameter semantics, the description is incomplete. It fails to address key context like dependencies (e.g., open browser), effects, or error conditions, leaving significant gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but only vaguely implies coordinates via 'specific coordinates'. It doesn't explain what 'x' and 'y' represent (e.g., screen pixels, relative positions), their units, or valid ranges. This adds little meaning beyond the bare schema.

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 ('Move') and resource ('mouse'), specifying the action of moving to coordinates. It distinguishes from siblings like 'mouseClick' or 'mouseDrag' by focusing solely on positioning without clicking or dragging. However, it doesn't explicitly differentiate from 'moveMouse' (a likely duplicate), slightly reducing specificity.

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. It doesn't mention prerequisites (e.g., needing an open browser), exclusions, or comparisons to similar tools like 'hover' or 'mouseDrag'. The agent must infer usage from the name alone.

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