Skip to main content
Glama

browser_double_click

Perform a double-click action on a web element using Selenium WebDriver. Specify element locator strategy and value to automate browser interactions for testing or automation workflows.

Instructions

Perform double click on an element

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byYesLocator strategy to find element
valueYesValue for the locator strategy
timeoutNoMaximum time to wait for element in milliseconds

Implementation Reference

  • Registers the browser_double_click MCP tool with input schema based on locatorSchema and a handler that delegates to ActionService.doubleClickElement
    server.tool(
      'browser_double_click',
      'Perform double click on an element',
      { ...locatorSchema },
      async ({ by, value, timeout = 15000 }) => {
        try {
          const driver = stateManager.getDriver();
          const actionService = new ActionService(driver);
          await actionService.doubleClickElement({ by, value, timeout });
          return {
            content: [{ type: 'text', text: 'Double click performed' }],
          };
        } catch (e) {
          return {
            content: [
              {
                type: 'text',
                text: `Error performing double click: ${(e as Error).message}`,
              },
            ],
          };
        }
      }
    );
  • Implements the double-click functionality by waiting for the element using the locator, then performing a doubleClick action with Selenium WebDriver.
    async doubleClickElement(params: LocatorParams): Promise<void> {
      const locator = LocatorFactory.createLocator(params.by, params.value);
      const element = await this.driver.wait(until.elementLocated(locator), params.timeout || 15000);
      const actions = this.driver.actions({ bridge: true });
      await actions.doubleClick(element).perform();
    }
  • Zod schema defining the input parameters for locating the element to double-click (by, value, optional timeout).
    export const locatorSchema = {
      by: z
        .enum(['id', 'css', 'xpath', 'name', 'tag', 'class', 'link', 'partialLink'])
        .describe('Locator strategy to find element'),
      value: z.string().describe('Value for the locator strategy'),
      timeout: z.number().optional().describe('Maximum time to wait for element in milliseconds'),
    };
  • Calls registerActionTools which includes the browser_double_click tool registration.
    registerActionTools(server, stateManager);
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'double click' but doesn't disclose effects (e.g., whether it triggers events, requires element visibility, or has side effects like navigation), rate limits, or error conditions, leaving significant gaps.

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, making it highly concise and front-loaded. It efficiently conveys the core action 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 mutation tool (double-click implies interaction), the description is incomplete. It lacks details on behavioral outcomes, error handling, or what constitutes success, making it inadequate for safe and effective use by an AI agent.

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%, providing clear documentation for all parameters (by, value, timeout). The description adds no additional parameter semantics beyond what the schema states, so it meets the baseline of 3 without compensating further.

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 'Perform double click on an element' clearly states the action (double click) and target (an element), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'browser_click' or 'browser_right_click' beyond the double-click action, missing explicit sibling distinction.

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?

No guidance is provided on when to use this tool versus alternatives like 'browser_click' or 'browser_right_click'. The description lacks context about typical use cases (e.g., for activating elements that require double-click interaction) or prerequisites, leaving usage 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/pshivapr/selenium-mcp'

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