Skip to main content
Glama

click

Click UI elements by ID or screen coordinates to interact with desktop applications. Use element IDs for reliable accessibility actions or coordinates when standard clicks trigger unintended behaviors.

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
Behavior5/5

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

No annotations provided so description carries full burden. Discloses critical behavioral traits: reliability hierarchy ('most reliable' vs coordinate fallback), silent failure mode ('Coordinate clicks always report OK even if nothing was hit'), and parameter constraints ('Cannot be combined with button="right"'). Also notes UI inspection convention (@(x,y) in listings).

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?

Well-structured with clear hierarchy: purpose → mode comparison → behavioral warning → Args documentation. Front-loaded with the essential choice (ID vs coordinates). Slightly verbose but appropriate for 5 parameters with complex interaction rules; no wasted sentences.

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 5 parameters, 0% schema coverage, and behavioral complexity (dual invocation paths, silent failures, validation rules), coverage is strong. Mentions output verification via sibling tools. Minor gap: could briefly acknowledge the output schema exists (e.g., 'returns status'), but behavioral coverage is thorough.

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 has 0% description coverage (titles only). Description compensates comprehensively via Args section: defines each parameter, specifies valid values ('left' or 'right'), default states, and critical inter-parameter logic ('use with y instead of element_id', mutual exclusivity constraint).

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?

Opens with specific verb+resource ('Click an element by ID, or at screen coordinates') and immediately distinguishes the two operational modes. The dual-path purpose is clear and differentiates from siblings like mouse_move or press_key.

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

Usage Guidelines5/5

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

Explicitly prescribes when to use each mode ('Pass element_id...most reliable' vs 'Pass x and y...useful when clicking by ID triggers unintended action'). References sibling tools for verification ('verify...with a screenshot or find()') and clarifies mutual exclusivity of parameters.

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