Skip to main content
Glama

ie_click

Clicks an element after automatically waiting for it, using id, CSS, XPath, name, link text, tag, or class; supports single, double, and right clicks in driver or async mode.

Instructions

Click an element (auto-waits). 'by' is id/css/xpath/name/link_text/tag/class. action: click (default) | double | right. mode: driver (a WebDriver click; the default unless IE_CLICK_MODE=async) | async. An async click is queued on the page's own timer, so the call does not wait for the click's handlers (only the usual 'wait' pause follows) and cannot block even if the click opens a dialog that would block a driver click. It is script-initiated: there is no mousedown/mouseup/focus, handlers that test for a user gesture can behave differently, and the pop-up blocker may block a window.open it triggers. double and right always use the driver. Over COM (target hwnd:/tab:) a click is always queued on the page's timer and synthetic (script events, not mouse input).

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": {
      "by": "<by>",
      "value": "<value>"
    },
    "name": "ie_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
modeNodriver | async (default: IE_CLICK_MODE, normally driver)
waitNoseconds to pause after the click (default 2)
frameNo
valueYes
actionNoclick | double | right
targetNoWhere to act: omit it for the session's IE driver; hwnd:<n> acts over COM on the window <n> (a modal dialog's hwnd from a NOTICE or ie_windows), tab:<n> on an attached tab. Over COM, DOM access is script, input is synthetic (script events and a timer click, not mouse or keyboard input; keys are posted window messages) and only id, name, tag, class, link_text and (documentMode 8+) css locators work.
timeoutNoseconds to wait for the element (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior5/5

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

No annotations are supplied, so the description carries the full burden and does so thoroughly: it discloses auto-waiting, that async clicks are queued on the page timer and do not wait for handlers, that synthesized clicks lack mousedown/mouseup/focus and can trip user-gesture checks and pop-up blockers, and that COM targets are always timer-queued and synthetic. These are exactly the behavioral caveats an agent needs before committing to a click strategy.

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 paragraph is front-loaded with the core action and locator/mode facts, and most parentheticals earn their place by carrying distinctions the schema does not. There is some repeated material — the COM timer-queue/synthetic behavior is stated in both the mode discussion and the closing sentence — and the run-on formatting makes it denser than it needs to be.

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?

For an 8-parameter, no-annotation, no-output-schema mutation tool, the definition covers the behaviorally risky dimensions (blocking, synthetic events, COM limitations, post-click wait, default click behavior). Gaps are modest: the 'frame' parameter and the exact relationship between 'timeout' and the auto-wait are not addressed, but nothing likely to cause a caller to misuse the tool is missing.

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

Parameters4/5

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

Schema coverage is 63%, and the description fills key gaps: it defines the accepted 'by' values (which the schema leaves undocumented), explains action's click/double/right variants, and notes that over COM only id, name, tag, class, link_text and css locators work. Frame is left unexplained by both schema and description, and the interaction between 'timeout' and 'auto-waits' is only implied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'Click an element (auto-waits)' — and immediately enumerates the locator strategies and click variants it supports. It does not explicitly contrast itself with siblings like ie_hover, ie_fill, or ie_press_key, so the agent must infer the boundary, but the action itself is unambiguous.

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?

Gives real selection guidance for the mode parameter: driver is the default and recommended path, async should be chosen when a click may open a blocking dialog, and double/right always fall back to driver. It stops short of saying when to reach for this tool instead of ie_js or ie_press_key, so the alternative-routing guidance is partial.

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