Click an element in a real Chrome/Chromium browser by snapshot reference or CSS selector to automate web interactions for AI agents.
Click an element by its snapshot reference (@1, @2, ...) or CSS selector.
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | Reference from snapshot (e.g. '@1') | |
| selector | No | CSS selector if ref is not used |
Changes observed during successful MCP inspections.
v0.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether clicking waits for the element, scrolls it into view, fails when the target is missing, or what side effects or return values to expect.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence that front-loads the action and immediately lists the two accepted targeting methods. There is no wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter click tool with no output schema, the description covers the essential invocation inputs. However, with no annotations it omits behavioral context such as snapshot prerequisites, element visibility requirements, and error handling that an agent may need.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already documents both parameters. The description restates the same targeting syntax without adding format details, fallback behavior between ref and selector, or constraints beyond what the schema provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Click) and resource (element) plus the two targeting mechanisms (snapshot ref or CSS selector). However, it does not distinguish this action from sibling tools like browser_fill or browser_press_key, so sibling differentiation is absent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use browser_click versus alternatives such as browser_fill, browser_press_key, or browser_mouse. The phrase 'snapshot reference' implies a prerequisite relationship with browser_snapshot but does not state it or clarify exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.