Skip to main content
Glama

scraping_browser_scroll

Scroll to the bottom of web pages to access dynamic content for web scraping and data collection with Bright Data Web MCP.

Instructions

Scroll to the bottom of the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full tool definition including handler function that uses page.evaluate to scroll to document.body.scrollHeight.
    let scraping_browser_scroll = {
        name: 'scraping_browser_scroll',
        description: 'Scroll to the bottom of the current page',
        parameters: z.object({}),
        execute: async()=>{
            const page = await (await require_browser()).get_page();
            try {
                await page.evaluate(()=>{
                    window.scrollTo(0, document.body.scrollHeight);
                });
                return 'Successfully scrolled to the bottom of the page';
            } catch(e){
                throw new UserError(`Error scrolling page: ${e}`);
            }
        },
    };
  • Input schema: no parameters required.
    parameters: z.object({}),
  • Tool is registered in the exported tools array.
    export const tools = process.env.API_TOKEN ? [
        scraping_browser_navigate,
        scraping_browser_go_back,
        scraping_browser_go_forward,
        scraping_browser_links,
        scraping_browser_click,
        scraping_browser_type,
        scraping_browser_wait_for,
        scraping_browser_screenshot,
        scraping_browser_get_text,
        scraping_browser_get_html,
        scraping_browser_scroll,
        scraping_browser_scroll_to,
    ] : [scraping_browser_activation_instructions];
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions scrolling behavior but lacks details on whether it waits for page load, handles infinite scroll, or has any side effects. This is a significant gap for a browser interaction tool.

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 no wasted words. It's front-loaded and efficiently communicates the core functionality.

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?

For a browser interaction tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after scrolling (e.g., does it return success/failure, wait for content, or handle errors), leaving critical behavioral context missing.

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 tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline high score.

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 to the bottom') and target ('current page'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling 'scraping_browser_scroll_to', which might offer more flexible scrolling options.

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 'scraping_browser_scroll_to' or other navigation tools. The description only states what it does, not when it's appropriate.

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/dsouza-anush/brightdata-mcp-heroku'

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