Skip to main content
Glama
seabassgonzalez

MCP Browser Screenshot Server

browser_navigate

Navigate to specified URLs to prepare web pages for automated screenshot capture, testing, or monitoring purposes.

Instructions

Navigate to a URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesURL to navigate to
waitUntilNoWhen to consider navigation completenetworkidle2

Implementation Reference

  • Handler for the browser_navigate tool. Ensures a browser page is available, navigates to the specified URL with optional waitUntil option, and returns a success message.
    case 'browser_navigate': {
      const { page } = await ensureBrowser();
      const url = args?.url as string;
      const waitUntil = (args?.waitUntil as any) || 'networkidle2';
    
      await page.goto(url, { waitUntil });
    
      return {
        content: [
          {
            type: 'text',
            text: `Navigated to ${url}`,
          },
        ],
      };
    }
  • Input schema for browser_navigate tool, requiring a URL and optionally specifying waitUntil navigation completion condition.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'URL to navigate to',
        },
        waitUntil: {
          type: 'string',
          enum: [
            'load',
            'domcontentloaded',
            'networkidle0',
            'networkidle2',
          ],
          description: 'When to consider navigation complete',
          default: 'networkidle2',
        },
      },
      required: ['url'],
    },
  • src/index.ts:107-131 (registration)
    Registration of the browser_navigate tool in the ListTools response, including name, description, and input schema.
    {
      name: 'browser_navigate',
      description: 'Navigate to a URL',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'URL to navigate to',
          },
          waitUntil: {
            type: 'string',
            enum: [
              'load',
              'domcontentloaded',
              'networkidle0',
              'networkidle2',
            ],
            description: 'When to consider navigation complete',
            default: 'networkidle2',
          },
        },
        required: ['url'],
      },
    },
  • Helper function ensureBrowser() used by browser_navigate handler to launch or reuse a Puppeteer browser and page instance.
    async function ensureBrowser(): Promise<{ browser: Browser; page: Page }> {
      if (!browserState.browser || !browserState.browser.isConnected()) {
        const headless = process.env.HEADLESS !== 'false';
        browserState.browser = await puppeteer.launch({
          headless,
          args: ['--no-sandbox', '--disable-setuid-sandbox'],
        });
        browserState.page = await browserState.browser.newPage();
      }
    
      if (!browserState.page || browserState.page.isClosed()) {
        browserState.page = await browserState.browser.newPage();
      }
    
      return {
        browser: browserState.browser,
        page: browserState.page,
      };
    }
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. 'Navigate to a URL' implies a navigation action but doesn't disclose behavioral traits such as whether it opens a new tab, handles redirects, requires an active browser session, or has any side effects like loading dependencies. This leaves significant gaps for an agent to understand the tool's behavior.

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 extremely concise with a single sentence 'Navigate to a URL', which is front-loaded and wastes no words. It efficiently conveys the core action without unnecessary elaboration, making it easy to parse.

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 navigation tool with no annotations and no output schema, the description is insufficient. It doesn't cover what happens after navigation (e.g., success/failure indicators, page state), prerequisites like needing a launched browser, or how it interacts with sibling tools. This leaves the agent with incomplete context for proper usage.

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%, so the schema already documents both parameters (url and waitUntil) with descriptions and enums. The description adds no additional meaning beyond what the schema provides, such as explaining the impact of waitUntil values on navigation timing. Baseline 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 'Navigate to a URL' clearly states the action (navigate) and target (URL), making the purpose understandable. However, it doesn't differentiate from sibling tools like browser_execute_script or browser_launch, which also involve browser navigation or interaction, so it lacks sibling distinction.

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. For example, it doesn't specify if this is for initial navigation after launching a browser or if it should be used instead of other navigation-related tools. There's no mention of prerequisites or exclusions.

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/seabassgonzalez/mcp-browser-screenshot'

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