veilbrowser

veil_click

Clicks a web element using its accessibility tree reference number with a human-like mouse movement path for stealth automation.

Instructions

Click an element by its snapshot ref (human-like mouse path).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ref": "<ref>"
    },
    "name": "veil_click"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.5.0Jul 29, 2026

TDQS

B3.1/5.0

Behavior2/5

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

Lacks behavioral details beyond 'human-like mouse path'. No disclosure of error handling, waiting behavior, scrolling into view, or side effects. Annotations are absent, so description carries full burden but falls short.

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?

One sentence with no filler. Efficient and to the point.

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

Completeness2/5

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

Given no annotations, no output schema, and a single parameter, the description is minimal. It omits typical click behavior (waiting, scrolling, return value) that an agent would need for correct invocation.

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

Parameters2/5

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

Single parameter 'ref' has no schema description (0% coverage). Description mentions 'snapshot ref' but does not explain what a snapshot ref is, how to obtain it, or its format. Should provide more context for such a critical parameter.

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?

Description clearly states action ('click'), target ('element by its snapshot ref'), and a behavioral nuance ('human-like mouse path'). It distinguishes from siblings like veil_click_at which uses coordinates.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like veil_click_at, veil_fill, or prerequisites such as needing a prior snapshot. Sibling tools include other click-like actions but no explicit context.

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