Skip to main content
Glama

Click

browser_click
Destructive

Clicks a page element by snapshot ref, refusing obscured, stale, or invisible targets and returning evidence of what changed.

Instructions

Click an element by ref. Refuses with a reason (obscured, stale, not visible) instead of clicking the wrong thing. Returns evidence of what changed.

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": {
      "ref": "<ref>"
    },
    "name": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesFrom the latest snapshot, e.g. "e12" or "f1e3"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, so the risk profile is covered. The description adds genuinely new behavior beyond that: it refuses rather than mis-clicking, enumerates refusal reasons (obscured, stale, not visible), and promises evidence of what changed — all useful for an agent deciding whether to retry or re-snapshot.

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?

Three short sentences, each carrying distinct information: the action, the failure mode with reasons, and the return contract. The key behavior (safe refusal) is front-loaded immediately after the action statement, with no filler.

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?

With no output schema, the description usefully fills the return-value gap by stating it returns evidence of what changed, and it covers failure semantics. Minor gaps remain, such as whether the click waits for navigation or how to react to a stale-ref refusal, but nothing critical is missing for a one-parameter action tool.

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?

The single `ref` parameter has 100% schema description coverage, including a format pattern and example ("e12" or "f1e3"). The description's "by ref" adds nothing beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb and resource ("Click an element by ref"), which is unambiguous and distinct from siblings like browser_type, browser_press, or browser_select. It does not explicitly name an alternative, so it falls just short of full sibling differentiation.

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?

Usage is implied by "Click an element by ref" plus the schema note that the ref comes from the latest snapshot, which tells an agent this is the action step after a snapshot. However, there is no explicit guidance on when to prefer click over browser_press, browser_select, or browser_actions, and no stated preconditions.

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