Skip to main content
Glama

browser_click

Clicks a single browser element resolved by hint, index, or name substring; defaults to dry run, so set go=true to execute the click.

Instructions

Click a single element resolved by --hint, --idx, or --name-contains. Default dry_run=true; set go=true to actually click.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browser_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
goNo
idxNo
hintNoVimium-style letter (a, s, aa, ..)
portNo
protocolNocdp
host_headerNoBiDi Host header; use localhost:9222 through SSH forwarding
control_typeNo
url_containsNo
name_containsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.3/5.0
Behavior3/5

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

With zero annotations the description carries the full burden, and it does disclose the most important behavioral trait: the default is a dry run and nothing happens until go=true. It says nothing about whether the click waits for the element, whether navigation/staleness can occur, what is returned, or what happens if the hint matches multiple elements.

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?

Two short sentences, zero filler, with the resolution mechanism and the safety default both front-loaded. It is arguably too terse for a 9-parameter tool, but nothing written is wasted.

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?

For a 9-parameter, no-annotation tool with no output schema, the description covers only target selection and the go flag; transport parameters, URL scoping, and post-click behavior are undocumented. An agent could call it correctly in the happy path but would be guessing on several inputs.

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 only 22% across 9 parameters, yet the description explains the three mutually alternative targeting parameters and the go toggle, which is the highest-value subset. url_contains, port, protocol, host_header and control_type are left entirely to bare schema fields, so it only partially compensates for the coverage gap. Minor mismatch: it refers to a '--dry_run' default that appears in the schema only as go=false.

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 (click) and resource (a single element) plus how the target is resolved (--hint, --idx, --name-contains), which pins down scope. It does not differentiate itself from the near-identically named siblings 'click' and 'click_by_id', so an agent cannot tell from the text alone which of the three to pick.

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?

The description gives one important usage rule: the tool is a no-op unless go=true is set, which is genuine invocation guidance rather than a restatement of the schema. It offers no when-to-use versus 'click' / 'click_by_id' / 'browser_type' guidance and no prerequisites (browser launched, page loaded, element visible).

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