Skip to main content
Glama

browser_scroll_to_top

Scroll to the top of the page during web automation. Use this tool to return to the page's starting position for consistent testing or navigation.

Instructions

Scroll to the top of the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The inline handler and registration for the 'browser_scroll_to_top' tool. It retrieves the WebDriver from StateManager, instantiates ActionService, and calls scrollToTop().
    server.tool('browser_scroll_to_top', 'Scroll to the top of the page', {}, async () => {
      try {
        const driver = stateManager.getDriver();
        const actionService = new ActionService(driver);
        await actionService.scrollToTop();
        return {
          content: [{ type: 'text', text: `Scrolled to top of the page` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error scrolling to top: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • The supporting method in ActionService that executes the JavaScript 'window.scrollTo(0, 0);' to scroll to the top of the page using the WebDriver.
    async scrollToTop(): Promise<void> {
      await this.driver.executeScript('window.scrollTo(0, 0);');
    }
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 doesn't describe traits like whether it's synchronous/asynchronous, if it requires a loaded page, potential errors (e.g., if no page is open), or side effects. 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, clear sentence with zero waste—'Scroll to the top of the page' directly conveys the action. It's front-loaded and appropriately sized for a simple, parameterless tool, making it highly efficient.

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 simplicity (0 params, no output schema) and lack of annotations, the description is minimally adequate. It states what the tool does but misses behavioral details like execution context or error handling. For a browser tool, this leaves gaps, but it's complete enough for basic understanding without being misleading.

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 doesn't add param info, but that's appropriate here. Baseline is 4 for 0 params, as the schema fully handles the lack of parameters without requiring description compensation.

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 the top of the page' clearly states the action (scroll) and target (top of page), making the purpose immediately understandable. It distinguishes from siblings like 'browser_scroll_to_bottom' or 'browser_scroll_by_pixels' by specifying the destination. However, it doesn't explicitly mention the browser context, which is implied but could be slightly more specific.

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 an open browser page), exclusions, or comparisons to siblings like 'browser_scroll_to_element' for targeted scrolling. Usage is implied by the action but lacks explicit context.

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