Skip to main content
Glama
Sign In
Browser MCP

Browser MCP

by drisplabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Select Option

select

Choose a dropdown menu option by its value or visible text using a stable element ID for reliable browser automation.

Instructions

Choose an option from a dropdown menu by value or visible text.

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": {
      "eid": "<eid>",
      "value": "<value>"
    },
    "name": "select"
  }
}

Input Schema

NameRequiredDescriptionDefault
eidYesElement ID of the dropdown from find results or the page snapshot.
valueYesThe option to select - can be either the value attribute or the visible text of the option.
page_idNoPage ID. If omitted, operates on the most recently used page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / page_id / description
      Added value: +"Page ID. If omitted, operates on the most recently used page."
  2. First observedv4.6.4

TDQS

A3.6/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 full burden. It does not disclose behavioral traits such as whether selection triggers events, validation of option existence, or any side effects. The description is too minimal for a tool without annotations.

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?

The description is a single, front-loaded sentence with no unnecessary words. Every phrase adds value.

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 simple selection tool with no output schema, the description covers the core action adequately. It lacks mention of prerequisites or error conditions, but given low complexity, it is nearly complete.

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 baseline is 3. The description restates the dual nature of the 'value' parameter (value attribute or visible text) which is already in the schema, adding no new semantic meaning beyond what the schema provides.

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?

The description clearly states the action ('Choose an option') and the target resource ('dropdown menu') with the specific method ('by value or visible text'). It effectively distinguishes from sibling tools like 'click' or 'type' which perform different actions.

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

Usage Guidelines3/5

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

The description implicitly conveys usage context (dropdown selection) but provides no explicit guidance on when to use this tool versus alternatives, nor any when-not conditions.

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

Deploy Server

Other Tools