Skip to main content
Glama
andytango
by andytango

wait_for_navigation

Wait for page navigation to complete before proceeding with browser automation tasks. Specify timeout and wait conditions for reliable script execution.

Instructions

Wait for the page to navigate to a new URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitUntilNo
timeoutNoTimeout in milliseconds
tabIdNoTab ID to operate on (uses active tab if not specified)

Implementation Reference

  • The handler function that executes the wait_for_navigation tool. It retrieves the page, waits for navigation with specified options, and returns the new URL and title or handles errors like timeout.
    async ({ waitUntil, timeout, tabId }) => {
      const pageResult = await getPageForOperation(tabId);
      if (!pageResult.success) {
        return handleResult(pageResult);
      }
    
      const page = pageResult.data;
      const timeoutMs = timeout ?? getDefaultTimeout();
    
      try {
        await page.waitForNavigation({
          waitUntil: (waitUntil ?? 'load') as WaitUntilOption,
          timeout: timeoutMs,
        });
    
        return handleResult(ok({
          url: page.url(),
          title: await page.title(),
        }));
      } catch (error) {
        if (error instanceof Error && error.message.includes('timeout')) {
          return handleResult(err(operationTimeout('wait_for_navigation', timeoutMs)));
        }
        return handleResult(err(normalizeError(error)));
      }
    }
  • Zod schema defining the input parameters for the wait_for_navigation tool: waitUntil, timeout (optional), tabId (optional).
    export const waitForNavigationSchema = z.object({
      waitUntil: waitUntilSchema,
      timeout: timeoutSchema,
      tabId: tabIdSchema,
    });
  • Registers the wait_for_navigation tool on the MCP server with description, schema, and handler function.
    server.tool(
      'wait_for_navigation',
      'Wait for the page to navigate to a new URL',
      waitForNavigationSchema.shape,
      async ({ waitUntil, timeout, tabId }) => {
        const pageResult = await getPageForOperation(tabId);
        if (!pageResult.success) {
          return handleResult(pageResult);
        }
    
        const page = pageResult.data;
        const timeoutMs = timeout ?? getDefaultTimeout();
    
        try {
          await page.waitForNavigation({
            waitUntil: (waitUntil ?? 'load') as WaitUntilOption,
            timeout: timeoutMs,
          });
    
          return handleResult(ok({
            url: page.url(),
            title: await page.title(),
          }));
        } catch (error) {
          if (error instanceof Error && error.message.includes('timeout')) {
            return handleResult(err(operationTimeout('wait_for_navigation', timeoutMs)));
          }
          return handleResult(err(normalizeError(error)));
        }
      }
    );
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. It mentions waiting for navigation but does not disclose behavioral traits such as what happens on timeout (e.g., error thrown), whether it blocks until navigation completes, or if it works with page loads versus single-page app transitions. This leaves significant gaps in understanding 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 a single, clear sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and efficient, making it easy for an agent 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 no annotations, no output schema, and incomplete parameter coverage (67%), the description is inadequate. It lacks details on return values, error handling, and behavioral nuances, making it insufficient for an agent to fully understand how to invoke and interpret results from this tool.

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 67% (2 out of 3 parameters have descriptions), and the description adds no additional parameter semantics beyond what the schema provides. It does not explain the meaning of 'waitUntil' options or when to use 'tabId', so it meets the baseline for moderate schema coverage without compensating for gaps.

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 ('Wait for the page to navigate') and the target ('to a new URL'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'wait' or 'wait_for_selector', which handle different waiting scenarios, so it falls short of a perfect score.

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 does not mention scenarios like after clicking a link or submitting a form, nor does it reference sibling tools such as 'wait' (general wait) or 'wait_for_selector' (wait for an element), leaving the agent without context for selection.

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/andytango/puppeteer-mcp'

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