Skip to main content
Glama

browser_select_option

browser_select_option
Idempotent

Selects options in a browser select element by matching values, enabling automated dropdown choices during web form tasks.

Instructions

Choose options in a select element by value.

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

Input Schema

NameRequiredDescriptionDefault
tab_idYes
valuesYes
frame_idNoChrome frame ID inside the tab from browser_get_frames. 0 is the top document, which is the default.
element_idYesOpaque element_id returned by browser_get_interactives.
session_idNoSession that owns the tab. Pass it on every call so the runtime can refuse a tab another session holds.
session_nameNoName for this conversation's Chrome tab group, so the tab bar reads as the task instead of a generated id. Sticky: pass it once when the name becomes clear, and again only to rename.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's bar is lower, but it adds nothing beyond them. It does not say what happens to previously selected options, whether multi-select is supported, or that a session may be refused if another session holds the tab. No contradiction with annotations.

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 free of waste, but its brevity comes at the cost of substance rather than from tight editing. It is under-specified for a six-parameter browser interaction tool.

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 six-parameter tool operating across tabs, frames and sessions with no output schema, the description is far too thin. It omits session/frame scoping context, the meaning of the values list, and any return or verification behavior, leaving the agent to reconstruct the contract from the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description explains none of the parameters. The 'values' array is undocumented in both schema and description, so an agent cannot tell whether it replaces or appends to the current selection, or whether multiple values are allowed for single-select elements. Only element_id, frame_id, session_id and session_name carry schema descriptions.

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+resource pair: choose options in a select element, with the qualifier 'by value'. That is enough to understand the operation, but it does not differentiate from siblings such as browser_select_text or browser_set_checked, 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, and no alternative is named. The phrase 'by value' hints that a label-text alternative (browser_select_text) exists, but the agent must infer that distinction rather than being routed to it.

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