safari-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_hover

Move the pointer over an element by its browser_snapshot ref to trigger hover states, tooltips, or menus before clicking.

Instructions

Hover over an element by ref from browser_snapshot. trusted: true uses real OS-level input and moves focus to Safari.

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

Input Schema

Name	Required	Description
`ref`	Yes	Element ref from browser_snapshot or browser_find, e.g. e12
`tabId`	No	Tab id from browser_tabs. Default: current tab.
`backend`	No	Backend: real = your Safari, driver = isolated safaridriver session. Default: session default.
`element`	No	Human-readable element description, for the output only
`trusted`	No	Use real OS-level input (focus moves to Safari). Default: false on real, true on driver.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden, and it does reveal one important side effect: trusted: true uses real OS-level input and moves focus to Safari. It does not say what hovering triggers in the page (tooltips, CSS state), whether it mutates anything, or what the response contains.

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 sentences, front-loaded with the action and ref source, followed by the notable trusted side effect. Nothing is wasted, though the second sentence is a near-duplicate of schema text.

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

Completeness4/5

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

For a simple interaction tool with a fully documented five-param schema and no output schema, the description plus schema gives enough to call it correctly. The remaining gap is what hover actually does to page state and what is returned, which is minor here.

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 five parameters are already documented in the schema, including the trusted default and backend semantics. The description only restates the trusted behavior already present in the schema and adds no new meaning for ref, tabId, backend, or element.

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 names a specific verb and resource ("Hover over an element") and ties the ref back to browser_snapshot, which distinguishes it from browser_click and browser_type by implication. It stops short of explicitly contrasting itself with the other interaction tools, so a 4 rather than a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by "by ref from browser_snapshot", telling the agent the prerequisite source of the ref. There is no explicit when-not guidance, no mention of alternatives such as browser_click, and no statement about what situations call for hover specifically.

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