Skip to main content
Glama
andresolbach

nodriver-mcp-server

Click element

click

Clicks an element by snapshot uid with real CDP events, appearing as a trusted user action. Auto-scrolls to the element and handles layout shifts.

Instructions

Click an element addressed by its snapshot uid.

This is the click you want in almost all cases — prefer it over click_at, because a uid survives layout shifts and raw coordinates do not. The element is scrolled into view automatically, so it need not be visible beforehand.

Sends real CDP input events, so the page sees isTrusted=true, which is the entire point of an undetected driver. Two situations force a scripted fallback (element.click() plus synthetic events, isTrusted=false): a touch-emulated target, where CDP mouse input can crash the renderer, and a CDP click that times out or errors. The response says so explicitly whenever that happens, so a detectable click is never silent. Every step is bounded at 10s, so a wedged page cannot hang the call.

On "unknown uid", take a fresh take_snapshot and retry with the new uid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYesElement uid from the most recent take_snapshot, e.g. "4_12". uids are invalidated whenever the page changes — if you get "unknown uid", take a fresh snapshot and retry with the new uid.
dbl_clickNoSend a double-click instead of a single click.
include_snapshotNoAppend a fresh page snapshot to the response. Worth it when this action changes the page and take_snapshot would be your next call anyway — it saves a round trip, at the cost of a much larger response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses rich behavioral traits beyond the annotations: it sends real CDP input events with isTrusted=true, explains the two fallback scenarios and their consequences, notes that every step is bounded at 10s, and states that fallbacks are never silent. This is exactly the kind of context annotations do not provide. No contradiction exists.

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 front-loaded with the core action, then delivers usage guidance and behavioral detail in an organized manner. Every sentence earns its place—there is no filler or repetition. The length is justified by the technical nuance it conveys.

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?

For a tool with 3 parameters and an output schema, the description covers all essential aspects: purpose, alternative tool, fallback behavior, timing constraints, and error recovery. The presence of an output schema means return values need not be described, so nothing critical is missing. The description is fully self-sufficient 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?

Although schema coverage is 100%, the description adds significant meaning beyond the raw parameter definitions. It explains why uids are reliable, how to handle 'unknown uid' with a fresh snapshot, and the trade-off of include_snapshot (saves a round trip at cost of larger response). This meaningfully enhances an agent's ability to use the parameters correctly.

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 opens with a specific verb and resource: 'Click an element addressed by its snapshot uid.' It clearly distinguishes this tool from the sibling click_at by stating it is preferred and explaining why (uid survives layout shifts). The purpose is immediately unambiguous.

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 description explicitly says to prefer this over click_at, provides the rationale, and details the specific situations (touch-emulated target, timeout/error) that force a scripted fallback. This gives clear when-to-use and when-not-to-use guidance, going beyond vague hints.

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/andresolbach/nodriver-mcp-server'

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