safari-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_click

Clicks a page element using its snapshot reference, enabling reliable Safari automation with real OS-level input that moves focus to Safari or an isolated driver session.

Instructions

Click an element by ref from browser_snapshot. trusted: true uses real OS-level input and moves focus to Safari.

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

Name	Required	Description
`ref`	Yes	Element ref from browser_snapshot or browser_find, e.g. e12
`tabId`	No	Tab id from browser_tabs. Default: current tab.
`backend`	No	Backend: real = your Safari, driver = isolated safaridriver session. Default: session default.
`element`	No	Human-readable element description, for the output only
`trusted`	No	Use real OS-level input (focus moves to Safari). Default: false on real, true on driver.
`doubleClick`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

B3.4/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 behavioral burden, and it does disclose one important side effect: trusted=true uses OS-level input and steals focus to Safari. However, it says nothing about waiting for element readiness, scroll-into-view, failure behavior for stale refs, or what a click returns.

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?

Two short sentences with the core action front-loaded and no filler. The second sentence is terse to the point of being cryptic ('trusted: true uses real OS-level input') rather than fully structured.

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 six-parameter, no-annotation, no-output-schema mutation tool, the description covers the primary action and one side effect. It leaves gaps around backend selection implications (real vs driver session), stale/ref failure handling, and click result reporting, which an agent would need to call this confidently.

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 83%, so the schema already documents ref, tabId, backend, element, and trusted in detail. The description's trusted note restates what the schema already says ('focus moves to Safari'), and it adds nothing about doubleClick, which is the one parameter with no description.

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 states a specific verb and resource ('Click an element by ref') plus the source of the ref ('from browser_snapshot'), which an agent can act on directly. It does not differentiate itself from siblings like browser_hover or browser_type, so it falls short of a 5.

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 via the prerequisite that the ref must come from browser_snapshot or browser_find. There is no explicit when-to-use-vs-alternatives guidance (e.g., click vs hover vs select_option) and no mention of when clicking is inappropriate.

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