Skip to main content
Glama

browser_scroll_to_bottom

Scroll to the bottom of a webpage to load dynamic content or access elements at the end of the page during browser automation.

Instructions

Scroll to the bottom of the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool registration and handler for 'browser_scroll_to_bottom'. Creates an ActionService instance and calls its scrollToBottom method, with standard try-catch error handling returning markdown content.
    server.tool('browser_scroll_to_bottom', 'Scroll to the bottom of the page', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        const actionService = new ActionService(driver);
        await actionService.scrollToBottom();
        return {
          content: [{ type: 'text', text: `Scrolled to bottom of the page` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error scrolling to bottom: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • Core implementation of scrolling to the bottom of the page using Selenium WebDriver's executeScript to run 'window.scrollTo(0, document.body.scrollHeight)'. Called by the tool handler.
    async scrollToBottom(): Promise<void> {
      await this.driver.executeScript('window.scrollTo(0, document.body.scrollHeight);');
    }
  • Top-level registration call for action tools, including browser_scroll_to_bottom, in the tools index file.
    registerActionTools(server, stateManager);
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 fails to describe how it behaves—e.g., whether it waits for page load, handles infinite scroll, or may trigger dynamic content. For a browser interaction tool with zero annotation coverage, this is a significant gap in transparency.

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—'Scroll to the bottom of the page'—front-loading the core action efficiently. It's appropriately sized for a simple tool with no parameters, making every word count without unnecessary elaboration.

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 low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate but incomplete. It states what the tool does but lacks behavioral details (e.g., how scrolling works, potential side effects) and usage context, which are needed for full agent understanding in a browser automation suite.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't mention parameters, and since there are none, it doesn't need to compensate for any gaps. A baseline of 4 is justified as the description aligns with the schema's simplicity.

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 ('scroll') and target ('to the bottom of the page'), which is specific and unambiguous. However, it doesn't explicitly differentiate from siblings like 'browser_scroll_to_top' or 'browser_scroll_by_pixels', though the distinction is implied by the name. It avoids tautology by not merely restating the tool name.

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 such as 'browser_scroll_to_top' or 'browser_scroll_to_element'. It lacks context about scenarios where scrolling to the bottom is appropriate, such as loading dynamic content or reaching page footers, leaving the agent to infer usage from the name 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