Skip to main content
Glama

scraping_browser_go_back

Navigate to the previous page in a web scraping session to revisit content or correct navigation errors during automated data collection.

Instructions

Go back to the previous page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The complete handler definition for the 'scraping_browser_go_back' tool, including the name, description, input parameters schema (empty object), and the execute function. The execute function retrieves the current browser page and calls page.goBack() to navigate back, then returns the new title and URL.
    let scraping_browser_go_back = {
        name: 'scraping_browser_go_back',
        description: 'Go back to the previous page',
        parameters: z.object({}),
        execute: async()=>{
            const page = await (await require_browser()).get_page();
            try {
                await page.goBack();
                return [
                    'Successfully navigated back',
                    `Title: ${await page.title()}`,
                    `URL: ${page.url()}`,
                ].join('\n');
            } catch(e){
                throw new UserError(`Error navigating back: ${e}`);
            }
        },
    };
  • Registration of the scraping_browser_go_back tool (line 309) within the conditional export of the tools array, which is only included if the API_TOKEN environment variable is 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?

No annotations are provided, so the description carries full burden. It states the action but doesn't disclose behavioral traits like whether this requires an active browser session, what happens if there's no history, error conditions, or side effects. The description is minimal and lacks operational context.

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. It's appropriately sized for a simple navigation command and front-loaded with the essential action.

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 parameters, no output schema, no annotations), the description is minimally adequate but lacks completeness. It doesn't address behavioral context like error handling or session requirements, which would be helpful for an agent invoking this tool.

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 parameter semantics (none exist), which is appropriate. Baseline is 4 for zero-parameter tools.

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 ('Go back') and target ('to the previous page'), providing a specific verb+resource combination. It distinguishes this from forward navigation (scraping_browser_go_forward) but doesn't explicitly differentiate from other navigation tools like scraping_browser_navigate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context (after navigating to a page, to return to the previous one) but doesn't provide explicit guidance on when to use this versus alternatives like scraping_browser_navigate or when not to use it (e.g., when there's no browser history). No prerequisites or sibling tool comparisons are mentioned.

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