seleniumbase-mcp

Official

Overview Schema Source Related Servers Discussions Admin

hover_action

Hover over a web element, then optionally click a secondary element or drag-and-drop the primary to a destination using SeleniumBase.

Instructions

Hover over an element, optionally click another, or drag-and-drop.

Use this tool for hover interactions, hover-triggered menus, and drag-and-drop operations.

Args: selector1: The primary element selector. For action="none", this is the element to hover over. For action="click", this is the element to hover over before clicking selector2. For action="drag_and_drop", this is the draggable source element.

selector2:
    The secondary element selector.
    Required for action="click", where it identifies the element
    revealed or targeted after hovering selector1.
    Required for action="drag_and_drop", where it identifies the
    destination/drop target.
    Not used for action="none".

action:
    - "none": Hover over selector1 only.
    - "click": Hover over selector1, then click selector2.
    - "drag_and_drop": Drag selector1 and drop it onto selector2.

Returns: A confirmation message describing the performed operation.

Tool selection: - Simple hover -> action="none". - Hover over one element and then click another -> action="click". - Drag one element onto another -> action="drag_and_drop".

Notes: For action="click", selector1 is the hover target and selector2 is the click target.

For action="drag_and_drop", selector1 is the source and selector2
is the destination.

Input Schema

TableJSON Schema

Name	Required	Default
`action`	No	none
`selector1`	Yes
`selector2`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.2.6Sep 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

The description discloses the main behaviors: hovering, clicking, dragging, dropping, and returning a confirmation message. It doesn't mention potential side effects like navigation or waiting, but with no annotations provided this is a reasonable level of transparency.

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?

The description is well organized with clear sections, but the Notes section repeats selector-role information already stated earlier. It is still concise enough to be easily parsed.

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

Completeness5/5

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

The description covers the action enum, selector requirements, tool-selection guidance, and return value. Given that no annotations or output schema were provided, this is a complete description for an agent to invoke the tool correctly.

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

Parameters5/5

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

Every parameter is thoroughly explained: selector1, selector2, and the action enum. The description states when selector2 is required and clarifies the role each selector plays for each action value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: hover over an element, optionally click another, or drag-and-drop. This distinguishes it from sibling tools like click and find_elements.

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

Usage Guidelines5/5

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

The Tool selection section explicitly maps use cases to action values: simple hover to none, hover-then-click to click, and drag-and-drop to drag_and_drop. This leaves no ambiguity about when to use each mode.

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