Skip to main content
Glama

scraping_browser_go_forward

Navigate forward to the next page in a web browsing session to continue data collection or automation workflows.

Instructions

Go forward to the next page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Full definition of the scraping_browser_go_forward tool object, including name, description, empty parameters schema (z.object({})), and execute handler that retrieves the browser page and calls page.goForward(), then returns success message with title and URL.
    const scraping_browser_go_forward = {
        name: 'scraping_browser_go_forward',
        description: 'Go forward to the next page',
        parameters: z.object({}),
        execute: async()=>{
            const page = await (await require_browser()).get_page();
            try {
                await page.goForward();
                return [
                    'Successfully navigated forward',
                    `Title: ${await page.title()}`,
                    `URL: ${page.url()}`,
                ].join('\n');
            } catch(e){
                throw new UserError(`Error navigating forward: ${e}`);
            }
        },
    };
  • Export of the 'tools' array that registers scraping_browser_go_forward (at line 310) among other browser tools, conditional on process.env.API_TOKEN being set.
    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?

With no annotations, the description carries full burden but only states the basic action. It lacks details on behavioral traits such as whether it requires an active browser session, what happens if no forward history exists (e.g., error or no-op), or if it affects page state (e.g., reloading). This is inadequate for a tool with potential side effects.

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 no wasted words. It's front-loaded and directly conveys the core action, 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 complexity of a browser interaction tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'next page' means in context (e.g., browser history), potential errors, or return values, leaving critical gaps for an agent to use it correctly.

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 doesn't add param info, which is fine, but it also doesn't compensate for any gaps since there are none. Baseline is 4 for zero parameters.

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 'Go forward to the next page' clearly states the action (go forward) and target (next page) with a specific verb. It distinguishes from siblings like 'scraping_browser_go_back' by direction, but doesn't fully differentiate from navigation tools like 'scraping_browser_navigate' in terms of scope or mechanism.

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. It doesn't mention prerequisites (e.g., requires a browsing session with forward history), exclusions, or comparisons to siblings like 'scraping_browser_navigate' for general navigation.

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