Skip to main content
Glama

reload

Refresh the current web page to reload content, update dynamic elements, or retry failed requests during browser automation.

Instructions

Reload the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'reload' MCP tool. It calls the browser's reload method and returns a success response.
    handler: async () => {
      await browser.reload();
      return { success: true, message: 'Page reloaded' };
    }
  • Input schema for the 'reload' tool, which requires no parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      required: []
    },
  • Registration of the 'reload' tool object within the createPlaywrightTools function's return array.
    {
      name: 'reload',
      description: 'Reload the current page',
      inputSchema: {
        type: 'object',
        properties: {},
        required: []
      },
      handler: async () => {
        await browser.reload();
        return { success: true, message: 'Page reloaded' };
      }
    },
  • The SimpleBrowser.reload() helper method invoked by the tool handler, using Playwright's page.reload().
    async reload() {
      await this.ensureLaunched();
      await this.page.reload();
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose important behavioral traits like whether this causes page state loss, triggers network requests, requires page load completion, or has any side effects. 'Reload' implies mutation but lacks safety/performance 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 wasted words. It's appropriately sized for a simple action and front-loads the essential information immediately.

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 browser interaction tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens after reloading (page load state, potential errors, completion signals) or how this differs from other navigation tools. Given the complexity of browser automation, more context is needed.

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 the schema already fully documents the empty parameter set. The description appropriately doesn't add parameter information beyond what's already covered, earning a baseline score of 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 ('Reload') and target ('the current page'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'navigate' or 'go_back' which also affect page state, so it doesn't reach the highest 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 like 'navigate' (for loading new URLs) or 'go_back'/'go_forward' (for browser history navigation). There's no mention of context, prerequisites, or exclusions for using this tool.

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/zypin-testing/zypin-mcp'

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