Playwright MCP

browser_select_option

Destructive

Select values in dropdown menus during browser automation. Specify element references and values to interact with web page select elements programmatically.

Instructions

Select an option in a dropdown

Input Schema

TableJSON Schema

Name	Required	Description
`element`	Yes	Human-readable element description used to obtain permission to interact with the element
`ref`	Yes	Exact target element reference from the page snapshot
`values`	Yes	Array of values to select in the dropdown. This can be a single value or multiple values.

Implementation Reference

src/tools/snapshot.ts:150-160 (handler)

The core handler function for the 'browser_select_option' tool. It resolves the element locator from the provided ref, adds corresponding Playwright code to the response, executes the selectOption action on the locator with the given values, and waits for completion.

handle: async (tab, params, response) => {
  response.setIncludeSnapshot();

  const locator = await tab.refLocator(params);
  response.addCode(`// Select options [${params.values.join(', ')}] in ${params.element}`);
  response.addCode(`await page.${await generateLocator(locator)}.selectOption(${javascript.formatObject(params.values)});`);

  await tab.waitForCompletion(async () => {
    await locator.selectOption(params.values);
  });
},

src/tools/snapshot.ts:136-148 (schema)

Defines the input schema (extending elementSchema with 'values' array) and the tool schema including name 'browser_select_option', title, description, inputSchema reference, and type.

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 = defineTabTool({
  capability: 'core',
  schema: {
    name: 'browser_select_option',
    title: 'Select option',
    description: 'Select an option in a dropdown',
    inputSchema: selectOptionSchema,
    type: 'destructive',
  },

src/tools.ts:36-52 (registration)

Registers the 'browser_select_option' tool by including the snapshot tools module (which exports it) in the central allTools array used by the backend.

export const allTools: Tool<any>[] = [
  ...common,
  ...console,
  ...dialogs,
  ...evaluate,
  ...files,
  ...install,
  ...keyboard,
  ...navigate,
  ...network,
  ...mouse,
  ...pdf,
  ...screenshot,
  ...snapshot,
  ...tabs,
  ...wait,
];

src/browserServerBackend.ts:48-59 (registration)

The BrowserServerBackend provides the tools list to MCP server and dispatches calls to the specific tool handler by name, enabling 'browser_select_option'.

tools(): mcpServer.ToolSchema<any>[] {
  return this._tools.map(tool => tool.schema);
}

async callTool(schema: mcpServer.ToolSchema<any>, parsedArguments: any) {
  const response = new Response(this._context, schema.name, parsedArguments);
  const tool = this._tools.find(tool => tool.schema.name === schema.name)!;
  await tool.handle(this._context, parsedArguments, response);
  if (this._sessionLog)
    await this._sessionLog.log(response);
  return await response.serialize();
}

src/browserServerBackend.ts:39-42 (registration)

Initializes the backend's _tools array using filteredTools, which includes the 'browser_select_option' tool.

constructor(config: FullConfig, browserContextFactory: BrowserContextFactory) {
  this._tools = filteredTools(config);
  this._context = new Context(this._tools, config, browserContextFactory);
}

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.3/5.0

Behavior3/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description doesn't contradict. However, the description adds no behavioral context beyond the annotations—it doesn't explain what 'destructive' means here (e.g., changes UI state), rate limits, or error handling. With annotations covering safety, a 3 reflects minimal added value.

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, efficient sentence with zero waste—it directly states the tool's purpose without redundancy. It's appropriately sized for a simple action tool and front-loaded with essential information.

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 (moderate, with destructive behavior), rich annotations, and no output schema, the description is minimally adequate. It covers the basic action but lacks details on outcomes, error cases, or integration with siblings like browser_snapshot for obtaining 'ref'. With annotations, it meets a baseline but could be more informative.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond implying dropdown interaction, which is already clear from the tool name. Baseline 3 is appropriate as the schema does the heavy lifting.

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 'Select an option in a dropdown' clearly states the action (select) and target (dropdown), distinguishing it from siblings like browser_click or browser_type. However, it doesn't explicitly differentiate from browser_handle_dialog which might also involve dropdowns, making it slightly less specific than a perfect 5.

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., requiring a page snapshot), exclusions, or comparisons to siblings like browser_click for non-dropdown interactions, leaving the agent to infer usage from context alone.

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