Skip to main content
Glama

human_click

Click web elements with a human-like cursor path using CSS selectors, numeric IDs, or visible text. Supports shadow DOM and custom elements.

Instructions

Click an element with a humanish cursor path.

    Accepts a CSS selector, the numeric ID from ``get_interaction_tree``,
    or visible text. ``move_duration`` is how long the mouse takes to
    reach the target (default 0.4s). Text-mode is shadow-DOM aware:
    the walker finds the tightest interactive element matching the
    text (descending into nested shadowRoots when needed) and aims
    the cursor at its composed viewport rect, so clicks land on the
    real handler inside custom elements like ``<nes-button>``.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo
selectorNo
move_durationNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It details the humanish cursor path, move_duration default, and shadow-DOM resolution mechanics. It does not mention potential behaviors like scrolling into view or error handling, but the provided context is substantial.

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 concise with four sentences, starts with the core purpose, and every sentence adds value. No redundant or extraneous information.

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

Completeness4/5

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

Given the output schema exists, return values need not be described. The tool covers parameters, behavior, and shadow-DOM handling. It lacks mention of error scenarios (e.g., element not found), but overall is sufficiently complete for a click action.

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?

Schema coverage is 0%, so the description fully compensates. It explains 'text' (numeric ID or visible text), 'selector' (CSS selector), and 'move_duration' (duration with default), adding meaning beyond the bare schema.

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 clearly states the tool clicks an element with a 'humanish cursor path', specifying the verb and resource while distinguishing from likely instant clicks like 'click' and 'mouse_click'. It also explains the unique shadow-DOM-aware text-mode, setting it apart from siblings.

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

Usage Guidelines3/5

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

The description implies usage for human-like interaction and shadow-DOM custom elements, but does not explicitly state when to use this tool over alternatives like 'click' or 'mouse_click'. No when-not-to-use or alternative suggestions are provided.

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/bituq/zendriver-mcp'

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