Skip to main content
Glama

playwright_hover

Simulate mouse hover interactions on web elements using CSS selectors for testing or automation workflows.

Instructions

Hover an element on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to hover

Implementation Reference

  • The HoverTool.execute method provides the core implementation of the playwright_hover tool, waiting for the selector and performing a hover action 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}`);
        });
      }
    }
  • JSON schema defining the input parameters for the playwright_hover tool, 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"],
      },
    },
  • Registration in the main tool handler switch statement that dispatches playwright_hover calls to the HoverTool instance.
    case "playwright_hover":
      return await hoverTool.execute(args, context);
  • Initialization of the global HoverTool instance in toolHandler.ts.
    if (!hoverTool) hoverTool = new HoverTool(server);
  • Codegen helper that generates Playwright test code for the hover action.
    case "playwright_hover":
      return this.generateHoverStep(parameters);
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 what 'hover' entails (e.g., mouse simulation, potential side effects like triggering CSS events, error handling if element not found, or performance implications). This is a significant gap for an interaction 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 with zero wasteโ€”it directly states the tool's function without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly.

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 complexity of a UI interaction tool with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after hovering (e.g., visual feedback, event triggers, or return values), leaving gaps in understanding the tool's full behavior and outcomes.

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?

The input schema has 100% description coverage, with the 'selector' parameter fully documented in the schema. The description adds no additional meaning beyond implying the selector targets an element to hover, which is already covered by the schema. This meets the baseline for high schema coverage.

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'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like playwright_click or playwright_drag, which are also element interaction tools, so it misses full sibling 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., requiring a page to be loaded), exclusions, or compare it to similar sibling tools like playwright_click or playwright_drag, leaving usage context implied at best.

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/aakashH242/mcp-playwright'

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