Skip to main content
Glama

browser_hover

Dispatch pointer hover events on a page element by selector or snapshot ref without moving the physical cursor, useful for revealing tooltips, menus, and hover-only states.

Instructions

Dispatch pointer and mouse hover events on an element. Does not move the physical cursor.

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>"
    },
    "name": "browser_hover"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
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.
revisionNoReject if the DOM revision differs from the snapshot.
selectorNoCSS selector. Must identify exactly one element.
inputModeNoAuto uses trusted Chrome text insertion only in the active foreground tab; DOM otherwise. Pointer actions and keys always use DOM.auto
documentIdNoReject the action if this snapshot document has changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one trait (no physical cursor movement) but says nothing about whether hover state persists, whether events are trusted or synthetic, required tab foregrounding, or side effects such as triggering menus or handlers.

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 tight sentences with the action front-loaded and the cursor caveat second. Nothing is redundant, though the caveat is somewhat vague about what 'physical cursor' means in a browser automation context.

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 an eight-parameter browser automation tool with no annotations and no output schema, the description is thin. It does not explain return behavior, hover persistence, or how failures (e.g., stale revisions, ambiguous selectors) are handled, leaving the agent to infer critical operational details.

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 all eight parameters including ref, selector, revision, and inputMode are already documented in the schema. The description adds no parameter-level meaning beyond that, which meets the baseline for fully documented schemas.

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: dispatching pointer/mouse hover events on an element. The clause 'Does not move the physical cursor' gives partial differentiation from sibling movement tools like browser_move or browser_click, though it does not name an alternative directly.

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 explicit guidance on when to use this instead of browser_move, browser_click, or browser_focus. The cursor note describes mechanism, not tool selection, so the agent must infer that hovering reveals hover-only UI such as tooltips or menus.

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