Back to docs

Tool Click

Category: Browser Automation · Tier: All

Click an element on the page. Pass _browserToken from the previous tool call to stay on the same page. Without it, clicks go to a blank new browser.

When to Use

Browser automation tools map to human motor interaction research. Click accuracy, form filling, and scroll behavior follow established HCI models.

Parameters

Parameter Type Required Description
selector string Yes Element to click (text content, CSS selector, or description)
force boolean No Allow clicking red-zone elements
verbose boolean No Return available elements on failure
_browserToken string No Browser session token from a previous call

Example

Click the "Sign Up" button on the landing page

Red-zone refusal

A click that would delete, pay or submit something is red zone. Without force: true it is refused and nothing is clicked. The response is a tool error (isError: true) in the shape every red-zone refusal uses:

Field Value
success false
tool "click"
zone "red"
target What the selector resolved to
message The gate's reason, then "Re-run with force: true (the MCP tool parameter; --force is the CLI flag)."
howToRun "Re-run with force: true (the MCP tool parameter; --force is the CLI flag)."

On the hosted server a refused call is refunded, because nothing was clicked. See Constitutional Safety for how the red zone is decided.

Tips

  • Pass _browserToken from a previous tool call to maintain the same browser session
  • The tool returns a _browserToken in its response — pass it to subsequent calls
  • Without _browserToken, each call gets a fresh browser (blank page)

Research

From the Blog