playwright-browser-hover
To hover over a page element, trigger hover states such as menus or tooltips.
When & Why to Use This Skill
The playwright-browser-hover skill enables Claude to interact with dynamic web elements by simulating precise mouse hover actions. It is designed to trigger hover-dependent UI states such as dropdown navigation menus, informative tooltips, and hidden overlays, allowing for seamless navigation and data extraction from complex, modern websites.
Use Cases
- Case 1: Accessing nested navigation links that are only visible when hovering over a primary menu item.
- Case 2: Triggering and capturing text from tooltips or hover-activated pop-ups to gather supplementary data during web research.
- Case 3: Automating UI testing by verifying that hover states (like color changes or visibility toggles) function correctly on a webpage.
- Case 4: Interacting with web-based dashboards where additional action buttons or metadata are revealed only upon mouse-over.
| name | playwright-browser-hover |
|---|---|
| description | "To hover over a page element, trigger hover states such as menus or tooltips." |
Usage
Use the MCP tool dev-swarm.request to send the payload as a JSON string:
{"server_id":"playwright","tool_name":"browser_hover","arguments":{}}
Tool Description
Hover over element on page
Arguments Schema
The schema below describes the arguments object in the request payload.
{
"type": "object",
"properties": {
"element": {
"type": "string",
"description": "Human-readable element description used to obtain permission to interact with the element"
},
"ref": {
"type": "string",
"description": "Exact target element reference from the page snapshot"
}
},
"required": [
"element",
"ref"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
Background Tasks
If the tool returns a task id, poll the task status via the MCP request tool:
{"server_id":"playwright","method":"tasks/status","params":{"task_id":"<task_id>"}}