Skip to main content
Glama

browser_hover

Hover over web elements to trigger interactive features during automated browser testing with Playwright sessions.

Instructions

Hover element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementYes
refYes

Implementation Reference

  • index.js:398-405 (registration)
    The 'browser_hover' tool is registered using `server.tool`. It validates the input using Zod and delegates the execution to `proxyToolCall`.
    server.tool('browser_hover', 'Hover element', {
      element: z.string(),
      ref: z.string()
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_hover', args);
    });
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 burden of behavioral disclosure. It fails to explain that this triggers mouseenter/hover events, whether it waits for hover effects to appear, or if it returns status. The agent cannot infer side effects or synchronous behavior.

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

Conciseness2/5

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

While brief (2 words), this is under-specification rather than appropriate conciseness. The description is too short to convey necessary information for a browser automation tool, failing to earn its utility through information density.

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?

Given 2 undocumented parameters, no output schema, no annotations, and the complexity of browser automation, the description is inadequate. It lacks critical context like element targeting syntax, timeout behavior, or session management details.

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

Parameters2/5

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

With 0% schema description coverage, the description must compensate but does not. It mentions 'element' (matching the parameter name) but gives no format guidance (CSS selector? XPath? ID?). It completely ignores the 'ref' parameter, leaving both parameters effectively undocumented.

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

Purpose2/5

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

The description 'Hover element' is essentially a tautology that restates the tool name ('browser_hover') with minimal elaboration. While it identifies the resource ('element'), it fails to specify what kind of hover (mouse hover) or distinguish from sibling tools like browser_click.

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 guidance provided on when to use hover versus click or other interaction methods. No mention of prerequisites (e.g., needing to navigate first) or typical use cases (revealing tooltips, dropdown menus).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server