Skip to main content
Glama
andytango
by andytango

reload

Reload the current web page in Puppeteer MCP Server to refresh content, handle dynamic updates, or reset page state for automated browser interactions.

Instructions

Reload the current page

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 reload tool: gets the page, calls page.reload() with options, returns updated URL and title, handles errors.
    async ({ waitUntil, timeout, tabId }) => {
      const pageResult = await getPageForOperation(tabId);
      if (!pageResult.success) {
        return handleResult(pageResult);
      }
    
      const page = pageResult.data;
    
      try {
        await page.reload({
          waitUntil: (waitUntil ?? 'load') as WaitUntilOption,
          timeout: timeout ?? getDefaultTimeout(),
        });
    
        return handleResult(ok({
          url: page.url(),
          title: await page.title(),
        }));
      } catch (error) {
        return handleResult(err(normalizeError(error)));
      }
    }
  • Zod schema defining the input parameters for the reload tool: waitUntil, timeout, tabId.
    export const reloadSchema = z.object({
      waitUntil: waitUntilSchema,
      timeout: timeoutSchema,
      tabId: tabIdSchema,
    });
  • Registration of the 'reload' tool on the MCP server using server.tool(), including name, description, schema, and handler.
    server.tool(
      'reload',
      'Reload the current page',
      reloadSchema.shape,
      async ({ waitUntil, timeout, tabId }) => {
        const pageResult = await getPageForOperation(tabId);
        if (!pageResult.success) {
          return handleResult(pageResult);
        }
    
        const page = pageResult.data;
    
        try {
          await page.reload({
            waitUntil: (waitUntil ?? 'load') as WaitUntilOption,
            timeout: timeout ?? getDefaultTimeout(),
          });
    
          return handleResult(ok({
            url: page.url(),
            title: await page.title(),
          }));
        } catch (error) {
          return handleResult(err(normalizeError(error)));
        }
      }
    );
  • src/server.ts:23-23 (registration)
    Top-level call to registerNavigationTools which includes the reload tool registration.
    registerNavigationTools(server);
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. 'Reload' implies a page refresh, but it doesn't disclose behavioral traits like whether it waits for page load, handles authentication persistence, affects browser state, or has 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, efficient sentence with zero waste. It's front-loaded and appropriately sized for a simple action, avoiding unnecessary elaboration. Every word earns its place.

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 3 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'reload' entails operationally, success/failure conditions, or interaction with browser state. For a tool with parameters and no structured safety hints, more context is needed.

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 of 3 parameters have descriptions). The description adds no parameter semantics beyond the schema. With moderate coverage, the baseline is 3, as the schema documents 'waitUntil' enum values, 'timeout' range/meaning, and 'tabId' default behavior, but the description doesn't enhance this.

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 'Reload the current page' clearly states the action (reload) and target (current page) with a specific verb+resource. It distinguishes from siblings like 'navigate' (loads a new URL) or 'go_back' (navigates back), but doesn't explicitly contrast with them. The purpose is unambiguous but could be more differentiated.

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 scenarios like refreshing content after dynamic updates, handling stale pages, or when to prefer 'navigate' to the same URL. With many browser interaction siblings, explicit usage context is missing.

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