BrowserMCP Extended

Overview Schema Source Related Servers Discussions Admin

browser_select_option

Select one or more values in a dropdown element using an exact snapshot reference and human-readable element description.

Instructions

Select an option in a dropdown

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

Input Schema

Name	Required	Description
`ref`	Yes	Exact element reference from the latest snapshot
`values`	Yes	Option values to select
`element`	Yes	Human-readable element description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 2, 2026

TDQS

C2.9/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 behavioral burden. It does not disclose whether selection triggers change events, whether multiple values imply multi-select, what happens if a value is not found, or whether it waits for the UI to settle.

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?

The single sentence is efficient and front-loaded with the verb and target. It is arguably too terse for a 3-parameter mutation-adjacent interaction, but there is no wasted text.

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?

For a tool that mutates page state with three required parameters, no annotations, and no output schema, the description omits important behavioral detail: failure modes, event side effects, and multi-select handling. An agent could call it, but with avoidable uncertainty.

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 the schema already documents ref, values, and element. The description adds no meaning beyond that baseline, so it neither compensates nor detracts.

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 ('Select') and resource ('an option in a dropdown'), which is clear enough for an agent to understand the operation. It does not, however, distinguish this tool from close siblings like browser_click or browser_type, which could also interact with form controls.

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 guidance on when to use this versus alternatives such as browser_click (e.g., for custom dropdowns not backed by a native <select>) or browser_type. No prerequisites, exclusions, or context are given.

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