Skip to main content
Glama

scraping_browser_navigate

Navigate a web scraping browser to a specified URL to access real-time web data for AI agents and LLMs.

Instructions

Navigate a scraping browser session to a new URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to navigate to

Implementation Reference

  • The complete handler implementation for the 'scraping_browser_navigate' tool. It defines the tool's metadata, input schema using Zod, and the execute function which obtains a browser page and navigates to the specified URL, returning navigation status, title, and current URL.
    let scraping_browser_navigate = {
        name: 'scraping_browser_navigate',
        description: 'Navigate a scraping browser session to a new URL',
        parameters: z.object({
            url: z.string().describe('The URL to navigate to'),
        }),
        execute: async({url})=>{
            const page = await (await require_browser()).get_page({url});
            try {
                await page.goto(url, {
                    timeout: 120000,
                    waitUntil: 'domcontentloaded',
                });
                return [
                    `Successfully navigated to ${url}`,
                    `Title: ${await page.title()}`,
                    `URL: ${page.url()}`,
                ].join('\n');
            } catch(e){
                throw new UserError(`Error navigating to ${url}: ${e}`);
            }
        },
    };
  • Zod schema defining the input parameter 'url' as a required string.
    parameters: z.object({
        url: z.string().describe('The URL to navigate to'),
    }),
  • The tool is registered by including it in the exported 'tools' array, which is conditionally populated based on the presence of the API_TOKEN environment variable.
    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 provided, the description carries the full burden of behavioral disclosure. While 'navigate' implies a state-changing operation, the description doesn't reveal important behavioral traits: whether this requires an existing session, what happens on navigation failure, if it waits for page load, or any rate limits/authentication needs. It provides minimal context beyond the basic action.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded with the essential information.

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 navigation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't address critical context: what constitutes a 'scraping browser session', whether navigation is synchronous/asynchronous, what happens on success/failure, or what (if anything) is returned. The description leaves too many operational questions unanswered.

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

Parameters3/5

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

Schema description coverage is 100% with the single 'url' parameter fully documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides (e.g., URL format requirements, validation rules, or examples). The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 ('navigate') and target ('a scraping browser session to a new URL'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'scraping_browser_go_back' or 'scraping_browser_go_forward', which are also navigation-related operations.

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., requires an active scraping browser session), when not to use it, or how it differs from other navigation tools in the sibling list like 'go_back' or 'go_forward'.

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