Skip to main content
Glama
dgutierrez1

concurrent-playwright-mcp

by dgutierrez1

Hover

browser_hover

Hover over an element in an isolated browser session using its reference from a browser_snapshot.

Instructions

Hover over an element (by ref from browser_snapshot).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesElement ref from the latest browser_snapshot (e.g. 'e12')
elementYesHuman description of the element (for logs/errors)
sessionIdYesId of the isolated browser session
Behavior2/5

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

No annotations provided, so description must convey behavioral traits. It only states the action without side effects, triggers, or error conditions. Missing details like whether it simulates a real hover or just moves cursor.

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?

Single sentence, minimal, front-loaded with purpose. No extraneous content.

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

Completeness3/5

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

Simple tool with full schema coverage; no output schema needed. However, lacks behavioral transparency and usage guidance, leaving gaps for an agent.

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 coverage is 100%, so baseline 3. Description adds minor value by referencing snapshot but doesn't elaborate on parameter formats or constraints beyond schema.

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?

Clear verb 'Hover over an element' with specific source 'by ref from browser_snapshot'. Distinguishes from sibling tools like browser_click and browser_type.

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

Usage Guidelines3/5

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

Implies need for prior snapshot but no explicit guidance on when to hover vs other interactions. No alternatives mentioned.

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

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