Skip to main content
Glama

Click

browser_click

Clicks an element identified by its snapshot ref and returns an updated snapshot so an AI agent can verify the action and continue.

Instructions

Click an element identified by its ref from the snapshot. After clicking, returns an updated snapshot.

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
refYesElement ref, e.g. '42'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one real behavioral trait: the call returns an updated snapshot, so the agent knows page state may change and a fresh snapshot comes back. It omits whether the click waits for navigation, what happens with stale or invalid refs, and any failure modes — meaningful gaps for an interactive tool with zero annotation coverage.

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?

Two short sentences, each doing distinct work: the action plus its input source, then the return behavior. The action is front-loaded and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema and no annotations, the description covers the core action and the notable side effect (updated snapshot in the response). It leaves callers without guidance on error handling for stale refs or whether navigation is awaited, which matters for reliable invocation in a browser automation loop.

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?

There is a single parameter with 100% schema description coverage, so the schema baseline already applies. The description adds only the provenance hint that the ref comes from a snapshot, which does clarify where valid values originate, but no format or lifecycle detail beyond that.

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 gives a specific verb+resource ('Click an element') and scopes it to refs from the snapshot, which separates it from navigation and read siblings. It stops short of contrasting with the closest siblings (browser_hover, browser_type), which also act on refs, so an agent must infer the distinction.

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 only implied: the phrase 'ref from the snapshot' signals a prerequisite ordering (snapshot first, then click), but there is no explicit when-to-use guidance or exclusion versus browser_hover or browser_type. Nothing is misleading, but nothing routes the agent either.

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