Skip to main content
Glama

browser_select

Select one or more options by value in a browser element and dispatch input/change events, with optional post-action checks for text, selector, URL, or timeout.

Instructions

Select options by their values and dispatch input/change events.

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

Input Schema

NameRequiredDescriptionDefault
refNoElement ref from the latest snapshot in this document.
tabIdYesTab id from browser_tabs.
expectNoPost-action condition. Default timeout is 1.2 seconds in visible pages and 3 seconds in hidden pages. A mismatch does not undo the action; inspect before retrying.
valuesYes
browserNoBrowser id from browser_list, or chrome/firefox when only one instance matches.
frameIdNoFrame id from browser_frames; defaults to top frame.
revisionNoReject if the DOM revision differs from the snapshot.
selectorNoCSS selector. Must identify exactly one element.
documentIdNoReject the action if this snapshot document has changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden, and it does disclose one meaningful behavior beyond the schema: that input/change events are dispatched, which matters for framework-bound selects. It omits error semantics, whether values must match existing option values, and the stale-snapshot rejection behavior that the schema parameters hint at but the description never mentions.

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 zero filler and no repetition of schema content. It is efficient, though the terseness borders on under-specification for a 9-parameter mutation tool.

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 9-parameter, nested-object, no-annotation mutation tool, one sentence is thin. The rich schema compensates for parameter detail, but nothing in the description covers prerequisites (snapshot/ref freshness), failure modes, or what happens when a value doesn't match an option.

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 89%, so the schema already documents tabId, ref, selector, values, browser, frameId, revision, documentId, and the nested expect object. The description adds only the nuance that matching is by option value rather than label — a small but real contribution above baseline.

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+resource ('Select options') plus the mechanism ('by their values and dispatch input/change events'), which implicitly separates it from the sibling browser_select_text (selection by visible text) and from browser_fill. It never explicitly names those siblings, so it stops 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance — nothing says this applies only to <select> elements, that a snapshot/ref must be obtained first, or which alternative to use when the target isn't a select. Usage is only inferable from the phrase 'select options'.

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