Skip to main content
Glama

browser_select_option

Destructive

Select options in dropdown menus during browser automation by specifying element references and values to choose.

Instructions

Select an option in a dropdown

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elementYesHuman-readable element description used to obtain permission to interact with the element
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.

Implementation Reference

  • The handler function that implements the core logic of the 'browser_select_option' tool. It retrieves the page snapshot, locates the target dropdown element, generates code for selecting options, and performs the selection using Playwright's locator.selectOption method.
      handle: async (context, params) => {
        const snapshot = context.currentTabOrDie().snapshotOrDie();
        const locator = snapshot.refLocator(params);
    
        const code = [
          `// Select options [${params.values.join(', ')}] in ${params.element}`,
          `await page.${await generateLocator(locator)}.selectOption(${javascript.formatObject(params.values)});`
        ];
    
        return {
          code,
          action: () => locator.selectOption(params.values).then(() => {}),
          captureSnapshot: true,
          waitForNetwork: true,
        };
      },
    });
  • Zod schema defining the input for 'browser_select_option': requires element description and ref from snapshot, plus array of values to select.
    const selectOptionSchema = elementSchema.extend({
      values: z.array(z.string()).describe('Array of values to select in the dropdown. This can be a single value or multiple values.'),
    });
    
    const selectOption = defineTool({
      capability: 'core',
      schema: {
        name: 'browser_select_option',
        title: 'Select option',
        description: 'Select an option in a dropdown',
        inputSchema: selectOptionSchema,
        type: 'destructive',
      },
  • Local registration of the 'browser_select_option' tool (as selectOption) within the array exported from snapshot.ts for further aggregation.
    export default [
      snapshot,
      click,
      drag,
      hover,
      type,
      selectOption,
    ];
  • src/tools.ts:35-50 (registration)
    Global registration: imports and includes all tools from snapshot.ts (including browser_select_option) into the snapshotTools array used by the MCP server.
    export const snapshotTools: Tool<any>[] = [
      ...common(true),
      ...console,
      ...dialogs(true),
      ...files(true),
      ...install,
      ...keyboard(true),
      ...navigate(true),
      ...network,
      ...pdf,
      ...screenshot,
      ...snapshot,
      ...tabs(true),
      ...testing,
      ...wait(true),
    ];
Behavior4/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, implying a write operation. The description aligns with this by describing a selection action that modifies the page state. It adds context about interacting with dropdowns, which is useful beyond the annotations, though it doesn't detail side effects like page reloads or validation.

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, direct sentence with no wasted words. It front-loads the core action and target efficiently, making it easy to parse quickly without unnecessary elaboration.

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

Completeness3/5

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

Given the tool's complexity (interactive UI action with destructive behavior) and lack of output schema, the description is minimal. It covers the basic purpose but misses details like error handling, return values, or dependencies on other tools (e.g., browser_snapshot for 'ref'), leaving gaps in completeness.

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 the schema fully documents parameters. The description adds no additional meaning about parameters beyond implying 'values' are for dropdown options, which is already clear from the schema. This meets the baseline for high schema coverage.

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 clearly states the action ('Select an option') and target ('in a dropdown'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like browser_click or browser_fill_form that might also interact with dropdowns, so it doesn't fully distinguish its unique scope.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a page snapshot from browser_snapshot), exclusions, or how it differs from similar tools like browser_click for dropdown interaction, leaving usage context unclear.

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/manishamishraacc/mcp'

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