Skip to main content
Glama

puppeteer_select

Select specific options in dropdown menus on web pages using CSS selectors to automate form interactions and data entry 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

  • Handler implementation for the puppeteer_select tool. Waits for the selector, selects the specified value in the dropdown, and returns success or error message.
    case "puppeteer_select":
      try {
        await page.waitForSelector(args.selector);
        await page.select(args.selector, args.value);
        return {
          content: [{
            type: "text",
            text: `Selected ${args.selector} with: ${args.value}`,
          }],
          isError: false,
        };
      }
      catch (error) {
        return {
          content: [{
            type: "text",
            text: `Failed to select ${args.selector}: ${error.message}`,
          }],
          isError: true,
        };
      }
  • Tool definition including name, description, and input schema for puppeteer_select, used for registration and validation.
    {
      name: "puppeteer_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"],
      },
    },
  • index.ts:447-449 (registration)
    Handler for listing tools, which includes puppeteer_select via the TOOLS array.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: TOOLS,
    }));
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but lacks details on what 'select' entails (e.g., does it simulate a user click, change a dropdown value, or trigger events?), potential side effects, error handling, or performance considerations. This is a significant gap for a tool that likely modifies page state.

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 waste. It front-loads the key action and target efficiently, making it easy to parse quickly. Every word contributes to understanding the tool's purpose 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 the complexity of interacting with web elements (likely involving state changes) and no annotations or output schema, the description is incomplete. It doesn't explain what happens after selection (e.g., does it return something, trigger page updates?), error cases, or dependencies. This leaves gaps for an agent to use the tool effectively in a browser automation 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 descriptions for both parameters (selector and value). The description adds no additional meaning beyond the schema, such as examples or constraints (e.g., valid CSS selector formats or value matching). Baseline 3 is appropriate since the schema adequately documents the parameters.

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'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like puppeteer_click or puppeteer_fill, which might also interact with page elements. The description is specific about the element type (Select tag) but could be more precise about what 'select' means in this context.

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 loaded), exclusions, or comparisons to siblings like puppeteer_fill for input fields. Without this context, an agent might struggle to choose between similar tools for interacting with web elements.

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/PhialsBasement/MCP-Puppeteer-Linux'

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