Skip to main content
Glama
Sign In
Fast Browser MCP

Fast Browser MCP

by kqlio67
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browser_click

Click a web element using its snapshot reference or CSS selector to automate browser interactions. Optionally wait for another element to appear after the click.

Instructions

Click an element by its snapshot reference (@1, @2, ...) or CSS selector.

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
refNoReference from snapshot (e.g. '@1')
trustedNoDispatch trusted CDP hardware mouse events (isTrusted: true)
selectorNoCSS selector if ref is not used
wait_forNoOptional CSS selector or @ref to wait for after clicking

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • addedInput schema / properties / trusted
      Added value: +{
+  "default": false,
+  "description": "Dispatch trusted CDP hardware mouse events (isTrusted: true)",
+  "type": "boolean"
+}
    • addedInput schema / properties / wait_for
      Added value: +{
+  "description": "Optional CSS selector or @ref to wait for after clicking",
+  "type": "string"
+}
  2. First observedv0.8.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and discloses almost nothing: no statement about scroll-into-view, auto-waiting for the element, failure behavior when the ref is stale or the selector matches nothing, or whether a click can trigger navigation. The only behavioral hint is the 'trusted' parameter documented in the schema, which the description never touches.

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 zero waste; the addressing modes come first. It is efficient but so terse that the brevity shades into under-specification rather than disciplined concision.

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 an interaction tool with no annotations and no output schema, an agent still needs to know what happens on a bad ref, whether the call blocks until the element is actionable, and what wait_for's failure mode is. None of that is covered, leaving real operational gaps.

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 coverage is 100%, so all four parameters (ref, selector, wait_for, trusted) are already documented with examples, including the '@1' notation the description repeats. The description adds no semantics beyond what the schema supplies, so the baseline of 3 applies.

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 concrete verb (Click) and resource (an element), plus the two accepted addressing modes (snapshot ref '@1' or CSS selector). An agent can distinguish it from browser_mouse or browser_fill without opening the schema, though it does not explicitly contrast with those siblings.

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?

No guidance on when to use a snapshot ref versus a CSS selector, no mention that browser_snapshot must be run first to obtain refs, and no note about re-snapshotting after a click that navigates. Usage is only implied by the parenthetical examples.

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

Deploy Server

Other Tools