Skip to main content
Glama

tab_select_option

Select an option in a native HTML dropdown on a browser page, firing input and change events so the page reacts. Use it when mouse clicks can't drive the macOS popup.

Instructions

Choose an option in a native dropdown of a page in the user's browser; tab_read lists its options. The macOS popup of a native select cannot be driven reliably by the mouse, so this sets the option the way the page would and fires its input and change events. Custom dropdowns built from other elements are not native selects: open them with tab_click and click the option. Returns what changed on screen.

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>",
      "option": "<option>"
    },
    "name": "tab_select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesElement ref: the number in brackets in tab_read output, e.g. 12 for "[12] button". Refs stay valid while the element stays on the page.
tabIdNoTab id from tab_list or tab_read. Defaults to the active tab of the browser window the user used last.
optionYesVisible label (case-insensitive) or value of the option to choose.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it explains why the tool exists (the macOS popup cannot be driven reliably by the mouse), that it sets the value the way the page would and fires input and change events, and that it returns what changed on screen. It does not cover failure behavior, such as what happens if the label/value matches no option or the element is not interactable.

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

Conciseness5/5

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

Three sentences, front-loaded with the action and scope, then the rationale, then the fallback path for the wrong element type. No restatement of the title or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation-style tool with no output schema, it covers the selection mechanism, the event semantics, the native-vs-custom distinction, and the return value at a high level. Only error and no-match behavior is left unaddressed.

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, tabId, and option are already documented, including that option accepts a case-insensitive visible label or value. The description's mention that tab_read lists options reinforces but does not extend the schema's own explanation of ref. Baseline 3 applies since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Choose an option in a native <select> dropdown') and immediately scopes it against a confusable case: custom dropdowns built from other elements are explicitly excluded. An agent can distinguish this from tab_click and tab_read without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit routing: use this for native selects, use tab_read to list options, and use tab_click plus an option click for custom dropdowns. Both the when and the when-not are named with the alternative tool for each.

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