Skip to main content
Glama

playwright_select

Select options from dropdown menus on web pages using CSS selectors and specified values for browser automation tasks.

Instructions

Select an element on the page with Select tag

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to select
valueYesValue to select

Implementation Reference

  • The SelectTool.execute method implements the core logic of the 'playwright_select' tool, waiting for the selector and calling page.selectOption.
    export class SelectTool extends BrowserToolBase {
      /**
       * Execute the select tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          await page.waitForSelector(args.selector);
          await page.selectOption(args.selector, args.value);
          return createSuccessResponse(`Selected ${args.selector} with: ${args.value}`);
        });
      }
    }
  • The input schema definition for the 'playwright_select' tool, defining required selector and value parameters.
    {
      name: "playwright_select",
      description: "Select an element on the page with Select tag",
      inputSchema: {
        type: "object",
        properties: {
          selector: { type: "string", description: "CSS selector for element to select" },
          value: { type: "string", description: "Value to select" },
        },
        required: ["selector", "value"],
      },
    },
  • Registration and dispatch of the 'playwright_select' tool in the main tool handler switch statement, calling the SelectTool's execute method.
    case "playwright_select":
      return await selectTool.execute(args, context);
  • Instantiation of the SelectTool instance used for handling 'playwright_select' tool calls.
    if (!selectTool) selectTool = new SelectTool(server);
  • Code generation helper method that produces Playwright test code for the 'playwright_select' tool action.
    private generateSelectStep(parameters: Record<string, unknown>): string {
      const { selector, value } = parameters;
      return `
      // Select option
      await page.selectOption('${selector}', '${value}');`;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: it doesn't specify if this requires a loaded page, whether it waits for the element, what happens on failure (e.g., timeout), or if it triggers page events. For a UI interaction tool with zero annotation coverage, this is insufficient.

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 zero 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.

Completeness2/5

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

Given no annotations, no output schema, and a UI interaction tool with potential side effects, the description is incomplete. It doesn't cover behavioral aspects like error handling, prerequisites, or return values, leaving significant gaps for an agent to use it correctly in context.

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%, with clear parameter descriptions in the schema. The description adds no additional meaning beyond implying the tool works with 'Select tag' elements, which loosely relates to the parameters but doesn't clarify syntax, format, or examples. 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 clearly states the action ('Select') and target ('element on the page with Select tag'), which is specific and unambiguous. It distinguishes from siblings like playwright_click or playwright_fill by focusing on selection operations for dropdown/select elements. However, it doesn't explicitly mention it's for dropdowns/select boxes, which would make it fully distinct.

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., requires a page to be loaded), contrast with similar tools like playwright_fill for input fields, or specify scenarios where selection is appropriate over other interactions.

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/aakashH242/mcp-playwright'

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