Skip to main content
Glama

browser_select_option

Selects specified values from dropdown or multi-select elements in browser automation sessions. Use this tool to interact with form elements during web testing or data extraction workflows.

Instructions

Select option

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementYes
refYes
valuesYes

Implementation Reference

  • index.js:407-415 (registration)
    Tool registration for 'browser_select_option', which uses proxyToolCall to delegate the execution.
    server.tool('browser_select_option', 'Select option', {
      element: z.string(),
      ref: z.string(),
      values: z.array(z.string())
    }, async (args) => {
      const check = requireActivePage();
      if (check) return check;
      return proxyToolCall('browser_select_option', args);
    });
  • The proxyToolCall function acts as the bridge for tool execution by delegating the call to the underlying MCP client instance.
    async function proxyToolCall(toolName, args) {
      log(`[proxyToolCall] ${toolName} with args: ${JSON.stringify(args)}`);
      const { client } = await getOrCreateInstance();
      log(`[proxyToolCall] got client for port ${assignedPort}`);
    
      // Update last used
      if (assignedPort && instances.has(assignedPort)) {
        instances.get(assignedPort).lastUsed = Date.now();
      }
    
      try {
        log(`[proxyToolCall] Calling client.callTool...`);
        const result = await client.callTool({ name: toolName, arguments: args || {} });
        log(`[proxyToolCall] Result type: ${typeof result}`);
        log(`[proxyToolCall] Result: ${JSON.stringify(result).slice(0, 500)}`);
    
        // The SDK returns { content: [...], isError?: boolean }
        // We need to return this same format
        if (result && result.content) {
          return result;
        }
    
        // Fallback: wrap in content array if needed
        return {
          content: [{ type: 'text', text: JSON.stringify(result) }]
        };
      } catch (error) {
        log(`[proxyToolCall] ERROR: ${error.message}\n${error.stack}`);
        return {
Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. It does not state whether this supports multi-select (implied by the array 'values' parameter), what happens if the option doesn't exist, whether it triggers change events, or what error conditions might arise.

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

Conciseness2/5

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

While brief at two words, this represents under-specification rather than efficient conciseness. The single sentence fails to earn its place by not adding value beyond the tool name, lacking the structured context needed for 3 undocumented parameters.

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

Completeness1/5

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

Completely inadequate for a browser automation tool with three undocumented parameters and no output schema. The description omits the element identification scheme, the browser context, multi-select support, and expected behavior—leaving the agent without sufficient context to invoke the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, requiring the description to compensate, but it mentions no parameters. The description fails to explain the distinction between 'element' and 'ref' identifiers, or that 'values' accepts an array presumably for multi-select capability—critical gaps for a 3-parameter tool.

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

Purpose2/5

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

The description 'Select option' is tautological given the tool name 'browser_select_option'. While it vaguely indicates the action (selecting) and target (options), it fails to specify that this is for dropdown/select elements, distinguish it from sibling tools like browser_click, or clarify the browser automation context.

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

Usage Guidelines1/5

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

No guidance provided on when to use this tool versus alternatives like browser_click or browser_type. Given siblings include multiple interaction methods, the description should specify this is specifically for <select> dropdown elements and when to prefer it over clicking.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/OMGEverdo/browser-pool-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server