Skip to main content
Glama

click

Triggers a browser element action by element reference or viewport coordinates to automate Firefox interactions, with button, modifier, and repeat options.

Instructions

Click an element by ref or by viewport coordinate.

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": {
      "tabId": "<tabId>"
    },
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoElement reference from read_page or find, e.g. "e12"
countNo2 for double click
tabIdYesTab ID, from tabs_list or tab_create
buttonNo
modifiersNoe.g. "ctrl", "shift", "ctrl+shift"
coordinateNo[x, y] in viewport CSS pixels, as seen in a screenshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosure, and it says nothing about whether the click waits for the element, scrolls it into view, can trigger navigation, or what happens on failure. For an interaction tool that mutates page state, this is a substantial gap.

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?

A single front-loaded sentence with no filler. It is efficient, but the brevity comes at the cost of the behavioral and usage detail noted elsewhere rather than being purely economical.

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?

With six parameters, no annotations, and no output schema, the description should explain mode selection and interaction semantics. It leaves the agent to infer the ref-versus-coordinate precedence and the effects of button, count, and modifiers entirely from the schema.

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

Parameters3/5

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

Schema description coverage is 83%, so the schema already documents ref, coordinate, count, tabId, and modifiers, and the baseline of 3 applies. The description confirms the two targeting alternatives but adds no precedence rule or format detail beyond what the schema states.

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?

The description names a specific verb (click) and resource (an element), and distinguishes the two targeting modes: by ref or by viewport coordinate. It is clear what the tool does, though it never contrasts itself with siblings like hover or form_input.

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?

There is no guidance on when to use this tool, when to use hover/type/form_input instead, or which targeting mode to prefer. The 'ref or coordinate' phrasing hints at two modes but gives no rule for choosing between them or for what happens if both are supplied.

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