Skip to main content
Glama
Brave Session MCP

Brave Session MCP

by MacStenk

brave_click

Destructive

Clicks a previously read element reference in a browser tab, optionally waits for navigation to settle, and reports updated checkbox, radio, or toggle state while bypassing overlay icons.

Instructions

Klickt eine zuvor gelesene Elementreferenz. Bei veränderten Element erneut lesen; nie blind wiederholen. wait wartet danach auf Navigation und Beruhigung, bevor zurückgekehrt wird. Bei Checkboxen, Radiobuttons und Schaltern wird ein überdeckendes Icon umgangen und der neue Zustand als checked gemeldet.

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

Input Schema

NameRequiredDescriptionDefault
refYesElementreferenz aus brave_read für genau diesen Tab.
waitNoMillisekunden, die nach der Aktion auf das Laden der Seite und eine Beruhigungsphase gewartet wird. Weglassen oder 0: sofort zurückkehren.
tabIdYesStabile Tab-ID aus brave_tabs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag a mutating, open-world, potentially destructive operation. The description adds real behavioral detail beyond them: wait blocks until navigation and a settling phase complete, and for checkboxes/radios/toggles an overlaying icon is bypassed with the new state reported as checked. It does not warn about what side effects a click can trigger, which is the main gap given destructiveHint=true.

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?

Four dense sentences, front-loaded with the action and then the critical safety rule about stale references. Nothing is padding, though the phrasing is terse enough that some transitions between the wait and checkbox behaviors are abrupt.

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?

For a three-parameter mutating click tool with no output schema, it covers the essential risks: stale refs, post-click waiting, and the special toggle-state reporting. Failure behavior and the nature of possible destructive side effects are left unstated.

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 100%, so ref, tabId and wait are already documented, including the load-and-settle semantics of wait. The description reinforces that ref must come from brave_read for this exact tab but adds little syntax or meaning the schema does not already carry; baseline 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 specific verb and resource: clicking an element reference previously obtained via brave_read. This implicitly separates it from brave_fill, brave_navigate and brave_read, but no sibling is named explicitly to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete usage rule — re-read when the element changed, never repeat blindly — and explains what the wait parameter means operationally. It lacks explicit routing guidance such as when to prefer brave_navigate or brave_fill over clicking, so the alternative-selection picture is incomplete.

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