Skip to main content
Glama

browser_move

Move a visible virtual cursor to viewport CSS coordinates so agents can target page elements without moving the physical mouse.

Instructions

Move the visible virtual cursor to viewport CSS coordinates. Does not move your physical mouse.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tabId": "<tabId>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "browser_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
tabIdYesTab id from browser_tabs.
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
inputModeNoAuto uses trusted Chrome text insertion only in the active foreground tab; DOM otherwise. Pointer actions and keys always use DOM.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does carry the full burden, and it does disclose two useful traits: the cursor is virtual/visible and physical mouse state is unaffected. It is silent on whether moving the cursor dispatches mouseover/hover events or otherwise changes page state, which is the main behavioral question an agent would have.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with the core action first and the physical-mouse caveat second. Nothing extraneous, though it is perhaps too lean for the amount of behavioral detail left unstated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter pointer tool with no annotations and no output schema, the definition covers the coordinate frame but omits event side effects and its relationship to sibling pointer tools. Adequate to invoke, thin for predicting consequences.

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 coverage is 67%, with x and y lacking descriptions in the schema; the phrase 'viewport CSS coordinates' fills that gap meaningfully. The remaining parameters (tabId, frameId, browser, inputMode) derive their meaning from the schema descriptions, not from this text.

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?

States a specific verb and resource (move the visible virtual cursor) and pins the coordinate space to viewport CSS coordinates. It does not distinguish itself from siblings like browser_hover, browser_click, or browser_drag, which an agent could easily confuse it with.

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 gives no when-to-use guidance, no exclusions, and never names an alternative. An agent must infer on its own whether to call this versus browser_hover for a hover intent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.