Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

select_option

Choose a specific option in an HTML dropdown using a CSS selector and value, enabling automated form selection in browser control workflows.

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": {
      "selector": "<selector>",
      "value": "<value>"
    },
    "name": "select_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
valueYesOption value to select
selectorYesCSS selector of the <select> element

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It does not say whether the element must be visible or focused, whether a change/input event is dispatched, what happens if the option value is absent, or how failures are reported.

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?

A single short sentence with the action and its target front-loaded; nothing is redundant. It is terse to the point of under-specification, but no wording is wasted.

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?

With no annotations and no output schema, the description is the only place behavioral and failure-mode detail could live, and it says nothing about them. For a 3-parameter browser automation action, the agent lacks information on prerequisites and error behavior.

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 all three parameters (tabId, selector, value) are already documented in the schema. The description adds no format details such as value-vs-label matching or how selector is resolved, so baseline 3 applies.

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 pair ("Select an option") constrained to a `<select>` dropdown, which lets an agent distinguish it from generic click/fill operations. It stops short of naming any sibling tool explicitly.

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?

The description gives no when-to-use or when-not-to-use guidance and never mentions alternatives like `fill`, `fill_form`, or `click`. The `<select>` constraint implies a use case, but nothing tells the agent how to choose between this and related form-filling tools.

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