Skip to main content
Glama

click

Click a UI element by its ID or at precise screen coordinates. Use element ID for reliable accessibility actions, or pass X and Y coordinates to avoid unintended actions like opening dropdowns.

Instructions

Click an element by ID, or at screen coordinates.

Pass ``element_id`` to click via the element's native
accessibility action (most reliable).  Pass ``x`` and ``y``
to click directly at screen coordinates instead — useful
when clicking by ID triggers an unintended action (e.g.
opens a dropdown instead of focusing a text entry).
Every element shows its position as @(x,y) in listings.
Coordinate clicks always report OK even if nothing was hit —
verify the result with a screenshot or find().

Args:
    element_id: The element ID to click.
    x: Screen X coordinate (use with y instead of element_id).
    y: Screen Y coordinate (use with x instead of element_id).
    button: "left" (default) or "right".
    double_click: If true, perform a double-click instead.
        Cannot be combined with button="right".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
element_idNo
xNo
yNo
buttonNoleft
double_clickNo

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 the full burden. It discloses that coordinate clicks always return OK even if nothing is hit, and that double_click cannot be combined with button='right'. It does not cover behavior like element visibility requirements or scroll-into-view, but the key quirks are addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear first sentence and logical flow. While slightly verbose, every sentence adds value. Front-loaded with the main purpose, then details on modes, caution, and parameter explanations.

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?

The description covers the essential contextual information: two click modes, pitfalls of coordinate clicks, and parameter constraints. Although an output schema exists (not shown), the description doesn't mention return values, but likely the schema covers that. Overall, it's complete for the tool's complexity.

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 must explain all parameters. It does so thoroughly: explains element_id vs x/y usage, button default and options, double_click behavior and incompatibility. This adds significant meaning beyond the raw 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's purpose: clicking an element by ID or at screen coordinates. It provides two distinct modes and explains when to use each, distinguishing it from sibling tools like 'focus' or 'mouse_move'.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use coordinates over element ID (e.g., when clicking by ID triggers an unintended action). It also warns about coordinate clicks always reporting success and recommends verification. However, it doesn't explicitly compare against other click-related siblings or mention when to use the tool itself via programmatic methods.

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/Touchpoint-Labs/Touchpoint'

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