Skip to main content
Glama

browser_scroll_to_element

Scrolls the browser viewport to locate and bring web elements into view using locator strategies like ID, CSS, or XPath for automated testing and interaction.

Instructions

Scroll to 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

  • Core implementation of scrolling to the element using Selenium WebDriver: locates the element and executes JavaScript 'scrollIntoView()'.
    async scrollToElement(params: LocatorParams): Promise<void> {
      const locator = LocatorFactory.createLocator(params.by, params.value);
      const element = await this.driver.wait(until.elementLocated(locator), params.timeout || 15000);
      await this.driver.executeScript('arguments[0].scrollIntoView();', element);
    }
  • Registers the MCP tool 'browser_scroll_to_element' with input schema based on locatorSchema and a handler that delegates to ActionService.scrollToElement.
    server.tool(
      'browser_scroll_to_element',
      'Scroll to an element',
      { ...locatorSchema },
      async ({ by, value, timeout = 15000 }) => {
        try {
          const driver = stateManager.getDriver();
          const actionService = new ActionService(driver);
          await actionService.scrollToElement({ by, value, timeout });
          return {
            content: [{ type: 'text', text: `Scrolled to element` }],
          };
        } catch (e) {
          return {
            content: [
              {
                type: 'text',
                text: `Error scrolling to element: ${(e as Error).message}`,
              },
            ],
          };
        }
      }
    );
  • Zod schema defining the input parameters for element locators: 'by' (strategy), 'value', and 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'),
    };
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 does not explain what 'scroll to' entails (e.g., smooth scrolling, immediate jump, visibility requirements), potential side effects, or error handling. This is inadequate for a tool that interacts with browser elements.

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 wasted words. It is front-loaded and directly conveys the core purpose without unnecessary elaboration, making it easy to parse quickly.

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 lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like how scrolling works, what happens if the element is not found, or the return value. For a tool with 3 parameters and no structured safety or output info, this minimal description leaves significant gaps.

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 'by' (locator strategy), 'value' (locator value), and 'timeout' (wait time). The description adds no parameter-specific information beyond the schema, so the baseline score of 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 'Scroll to an element' clearly states the action (scroll) and target (element), which is specific and unambiguous. However, it does not differentiate from sibling tools like 'browser_scroll_by_pixels', 'browser_scroll_to_bottom', etc., which also involve scrolling but with different targets or methods.

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 does not mention sibling scrolling tools (e.g., 'browser_scroll_by_pixels' for pixel-based scrolling) or prerequisites, 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.

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