Skip to main content
Glama
pvinis
by pvinis

playwright_hover

Simulate mouse hover interactions on web elements using a CSS selector. Enables precise testing and automation in a real browser environment.

Instructions

Hover an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to hover

Implementation Reference

  • The execute method of HoverTool class implements the core logic for the playwright_hover tool: waits for the selector and hovers over the element using Playwright's page.hover.
    export class HoverTool extends BrowserToolBase {
      /**
       * Execute the hover tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          await page.waitForSelector(args.selector);
          await page.hover(args.selector);
          return createSuccessResponse(`Hovered ${args.selector}`);
        });
      }
    }
  • Tool definition including name, description, and input schema requiring a CSS selector.
      name: "playwright_hover",
      description: "Hover an element on the page",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for element to hover" },
        },
        required: ["selector"],
      },
    },
  • Dispatch case in handleToolCall switch statement that routes playwright_hover calls to the HoverTool instance.
    case "playwright_hover":
      return await hoverTool.execute(args, context);
  • src/tools.ts:412-412 (registration)
    Inclusion in BROWSER_TOOLS array used to conditionally launch browser for tools requiring it.
    "playwright_hover",
  • Import of HoverTool class used in toolHandler.ts.
    HoverTool,
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on effects (e.g., triggers hover events, may reveal tooltips), error handling, or dependencies (e.g., requires a loaded page). This leaves significant gaps for a mutation tool.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's function without any wasted words. It is front-loaded and appropriately sized for a simple action, earning full marks for conciseness.

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 the tool's mutation nature (hovering implies interaction) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral outcomes, error cases, or return values, which are critical for an AI agent to use it correctly in a Playwright context.

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%, with the single parameter 'selector' documented as 'CSS selector for element to hover'. The description adds no additional meaning beyond this, such as selector syntax examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 clearly states the action ('hover') and target ('an element on the page'), which is specific and unambiguous. However, it doesn't distinguish this tool from its many sibling Playwright tools (like playwright_click or playwright_drag) beyond the hover action itself, missing explicit differentiation.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active page), exclusions, or compare it to similar tools like playwright_click for interactions, leaving usage context implied rather than explicit.

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

Related 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/pvinis/mcp-playwright-stealth'

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