agent-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_click

Click elements in a browser using CSS selectors, text, or snapshot refs to interact with pages and advance automation tasks.

Instructions

Click on an element identified by selector or ref (e.g., '@e1' from 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": {
      "selector": "<selector>"
    },
    "name": "browser_click"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes	CSS selector, text, or ref from snapshot (e.g., '@e1')
`sessionId`	No	Browser session ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 14, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, and the description only says 'click' without disclosing behavioral traits such as waiting for actionability, error handling, or potential navigation side effects. This leaves a significant transparency gap for an interactive browser tool.

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?

The description is a single, front-loaded sentence that conveys the core purpose and a clarifying example without any wasted words or unnecessary detail.

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 simple click action, the description covers the basic mechanism, but given the lack of annotations and output schema, it would benefit from additional context such as default behavior, return value, or dependency on the current page/session. It is adequate yet leaves clear gaps in completeness.

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 input schema already fully describes both parameters with high coverage (100%), including the selector's allowed forms (CSS selector, text, or ref). The description repeats the ref example but adds no new semantic meaning beyond what the schema provides, matching the baseline for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Click') and the resource ('an element'), and specifies the identification method (selector or ref with example '@e1' from snapshot). This distinguishes it from sibling interaction tools like browser_hover and browser_fill.

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 does not explicitly state when to use this tool versus alternatives. Usage context is implied by the name and sibling set, but there is no direct guidance or exclusions, so it relies on the user to infer.

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