safari-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_select_option

Selects one or more options in a select element using an element reference, enabling form and filter interactions in Safari.

Instructions

Select one or more options in a select element.

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>",
      "values": "<values>"
    },
    "name": "browser_select_option"
  }
}

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.
`values`	Yes
`backend`	No	Backend: real = your Safari, driver = isolated safaridriver session. Default: session default.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing. It does not say whether values are matched by option label, value attribute, or index, whether multiple selection requires a multi-select element, whether the change fires events, or what happens when a requested value is absent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and wastes no words, but at twelve words it is under-specified rather than well-structured. There is no hierarchy or added clause about behavior, so brevity here is a liability rather than an efficiency.

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?

This is a state-mutating browser automation tool with no annotations and no output schema, and one required parameter ('values') is undocumented. An agent lacks the information needed to know how values are interpreted or what failure looks like, so the definition is not complete enough for reliable invocation.

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 75%: ref, tabId, and backend are documented in the schema with useful detail (ref pattern and source, tab default, backend semantics). The description adds nothing beyond that, and the required 'values' array has no description in either place, leaving the matching semantics unexplained — but the baseline of 3 applies given the mostly-covered schema.

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 gives a specific verb ('Select') and resource ('options in a select element'), so an agent can identify the operation immediately. It does not contrast itself with close siblings like browser_fill_form or browser_click, which could plausibly also set a select value.

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?

There is no when-to-use guidance at all: nothing says to prefer this over browser_fill_form for dropdowns, no prerequisite that a snapshot must be taken first to obtain the ref, and no note on when to use backend=driver vs real. The agent must infer all routing decisions.

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