nodriver-mcp-server

Overview Schema Source Related Servers Discussions Admin

Click at coordinates

click_at

Clicks a raw viewport coordinate on canvases, maps, or video players that lack an addressable element. Uses real CDP events for precise control.

Instructions

Click a raw viewport coordinate instead of an element.

Use click with a uid whenever the target shows up in a snapshot — it is robust against layout shifts, this is not. Coordinates are for surfaces with no addressable element: canvases, maps, video players, image hotspots.

The point must lie inside the current viewport; scroll_page or scroll_to_selector first if it does not. Coordinates are in CSS pixels and ignore the device pixel ratio, so they match what emulate/resize_page report.

Same input path as click: real CDP events, the same reported scripted fallback, the same 10s bound per step.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`x`	Yes	X coordinate in CSS pixels, relative to the viewport's top-left corner.
`y`	Yes	Y coordinate in CSS pixels, relative to the viewport's top-left corner.
`browser`	No	Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.	default
`dbl_click`	No	Send a double-click instead of a single click.
`include_snapshot`	No	Append 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

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.5.0Sep 25, 2026

addedInput schema / properties / browser

Added value: +{
+  "default": "default",
+  "description": "Which browser to act on. Each name is an independent Chrome, created on first use. Omit for the shared default; parallel agents each need their own name.",
+  "type": "string"
+}

First observedv1.7.2Aug 7, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds substantial behavioral context beyond those: it warns that coordinate clicks are not robust against layout shifts, clarifies that coordinates are in CSS pixels and ignore device pixel ratio, requires the point to be inside the viewport, and notes 'Same input path as `click`: real CDP events, the same reported scripted fallback, the same 10s bound per step.' This fully discloses the behavioral profile without contradicting any annotation.

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 five sentences, each densely informative. It front-loads the core purpose and the key differentiator from `click`, then covers usage scope, coordinate constraints, and behavioral parity. There is no filler or repetition; every sentence earns its place.

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?

The tool has an output schema, so return value documentation is not required. The description covers the essential context for correct invocation: the target use cases, the distinction from `click`, the viewport requirement, the coordinate system, the robustness caveat, and the behavioral parity with `click`. For a 5-parameter tool with a rich sibling set, nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% (all 5 parameters have descriptions), so the baseline is 3. The description adds meaningful semantics for x and y by stating 'Coordinates are in CSS pixels and ignore the device pixel ratio, so they match what emulate/resize_page report' and by explaining the viewport requirement. It does not elaborate on browser, dbl_click, or include_snapshot beyond the schema, but those are already well-documented. The added coordinate semantics justify a slight bump to 4.

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 a raw viewport coordinate instead of an element.' It immediately distinguishes from the sibling 'click' by contrasting coordinate-based vs. element-based targeting. The subsequent sentence, 'Use `click` with a uid whenever the target shows up in a snapshot — it is robust against layout shifts, this is not,' explicitly names the sibling and the deciding condition, leaving no ambiguity about what this tool does.

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 gives explicit when-to-use and when-not-to-use guidance. It states coordinates are for 'surfaces with no addressable element: canvases, maps, video players, image hotspots' and that `click` should be used when a snapshot shows the target. It also provides a prerequisite: 'scroll_page or scroll_to_selector first if it does not [lie inside viewport].' This is model guidance for choosing the right tool.

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

Deploy Server