Skip to main content
Glama
Sign In
sandboxed-browser-mcp

sandboxed-browser-mcp

by smkamranqadri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Click

browser_click

Clicks or double-clicks a page element by its snapshot ref and reports the resulting screen changes, navigations, or newly opened tabs.

Instructions

Clicks, or with double: true double-clicks, the element with the given ref. Reports the changes on screen, or the new page when the tab moved, or the new tab when one opened.

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
refYesRef of the element to click (e12, f2e7 …), as browser_snapshot or browser_find showed it.
doubleNotrue for a double-click.
profileNoWhich browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / properties / profile
      Added value: +{
+  "default": "default",
+  "description": "Which browser profile (a separate signed-in session) to use. Leave it out for the default one; name another only when the user's task names it. Profiles: default.",
+  "type": "string"
+}
  2. Changed4 schema fields changedv1.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / double / default
      Added value: +false
    • changedInput schema / properties / double / description
      Previous value: -"Double-click; default false"New value: +"true for a double-click."
    • changedInput schema / properties / ref / description
      Previous value: -"Element ref from the latest view or browser_find, e.g. e12 (f1e5 inside a frame)"New value: +"Ref of the element to click (e12, f2e7 …), as browser_snapshot or browser_find showed it."
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description carries the burden of explaining effects. It does so well, disclosing that a click reports on-screen changes, may move the tab to a new page, or may open a new tab — context that materially warns of side effects. It stops short of mentioning waits, failures, or blocked 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?

One front-loaded sentence with no filler, and the outcome-reporting clause is placed where it matters. The phrasing 'Clicks, or with double: true double-clicks' is slightly awkward but compact.

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?

With no output schema, the description usefully sketches possible results. However, for a mutating, open-world action tool it omits failure modes and timing concerns, so an agent still lacks guidance on what to do when a click has no visible effect.

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 ref, double, and profile are already fully documented, and the description's restatement of 'double: true' adds nothing new. Baseline 3 applies where the schema does the heavy lifting.

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 (the element with the given ref), and extends it with the double-click variant. It is clearly distinguishable from siblings like browser_type, browser_key, and browser_scroll, though it does not explicitly name any alternative.

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?

No explicit when-to-use or when-not-to-use guidance is given. The only procedural hint is that the ref comes 'as browser_snapshot or browser_find showed it', which implies a snapshot-first workflow but leaves the agent to infer it.

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