Skip to main content
Glama
Novpix

browsermcp-plus

by Novpix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_select_option

Destructive

Selects one or more options in a dropdown using an element reference, enabling AI clients to complete forms and menus in the user's Chrome browser.

Instructions

Select an option in a dropdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refYesExact target element reference from the page snapshot
valuesYesArray of values to select in the dropdown. This can be a single value or multiple values.
elementYesHuman-readable element description used to obtain permission to interact with the element
snapshotNoAlso return the page snapshot after the action (default: no). Use it when you need to see the result right away.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • addedInput schema / properties / snapshot
      Added value: +{
+  "description": "Also return the page snapshot after the action (default: no). Use it when you need to see the result right away.",
+  "type": "boolean"
+}
  2. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this mutates page state. The description adds nothing on top of that: it does not say the page state changes, whether prior selections are replaced or appended, or what the element/reference permission flow entails.

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 zero waste and the action front-loaded. It is efficient, though the brevity is under-specification rather than deliberate conciseness.

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 four-parameter, three-required mutation tool with no output schema, the description omits key context: how values map to option values vs. visible labels, whether multiple values require a multi-select, and how the element string is used for permission. Annotations cover the safety profile but not the invocation details.

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 four parameters (ref, values, element, snapshot) are already documented in the schema; baseline is 3. The description's only contribution is the word "dropdown", which loosely contextualizes "values" but adds no format or matching semantics beyond the schema.

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 and resource ("Select an option in a dropdown"), so an agent knows the action is a selection rather than a click or a free-text entry. It does not, however, distinguish this from close siblings like browser_click, browser_type, or browser_fill_form, which could also appear to interact with form controls.

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 statement of when to use this tool versus browser_click, browser_type, or browser_fill_form, and no prerequisites or exclusions. The only implied guidance is the word "dropdown", which the agent must infer means an HTML select-style control.

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