Skip to main content
Glama

reload

Reload specific Firefox browser tabs using tab IDs to refresh content during automation or debugging processes on the Firefox MCP Server.

Instructions

Reload page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tabIdNo

Implementation Reference

  • The main handler function for the 'reload' tool. It ensures the browser is running, gets the page for the specified or active tabId, calls page.reload() using Playwright, and returns a success message.
    async reload(args = {}) {
      this.ensureBrowserRunning();
      const { tabId } = args;
      const page = this.getPage(tabId);
      await page.reload();
      
      return {
        content: [{
          type: 'text',
          text: `Page reloaded in tab '${tabId || this.activeTabId}'`
        }]
      };
    }
  • Tool registration entry including name, description, and input schema (optional tabId string). This defines the tool for the MCP server.
    {
      name: 'reload',
      description: 'Reload page',
      inputSchema: {
        type: 'object',
        properties: { tabId: { type: 'string' } }
      }
  • Dispatch logic in the MCP CallToolRequestHandler switch statement that routes 'reload' calls to the handler method.
    case 'reload':
      return await this.reload(args);
  • Input schema definition for the reload tool, allowing optional tabId.
    inputSchema: {
      type: 'object',
      properties: { tabId: { type: 'string' } }
    }
Behavior1/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 of behavioral disclosure. 'Reload page' implies a mutation (refreshing content), but it doesn't specify effects like page state changes, network requests, or potential side effects. It offers no behavioral details 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 extremely concise with just two words, front-loading the core action. There's no wasted text, though this brevity contributes to underspecification rather than clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's mutation nature (reloading implies change), no annotations, no output schema, and 1 undocumented parameter, the description is severely incomplete. It doesn't address behavior, parameters, or outcomes, making it inadequate for effective use.

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

Parameters2/5

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

The input schema has 1 parameter (tabId) with 0% description coverage, and the description adds no parameter information. It doesn't explain what 'tabId' is, how to obtain it, or its role in reloading, failing to compensate for the schema's lack of documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Reload page' restates the tool name 'reload' with minimal elaboration, making it a tautology. It doesn't specify what resource is being reloaded (e.g., a browser tab) or distinguish it from sibling tools like 'navigate' or 'back', though the context suggests it's for browser/page operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'navigate' (for new URLs) or 'back'/'forward' (for history navigation). The description lacks any context, prerequisites, or exclusions, leaving usage unclear.

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

Related 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/JediLuke/firefox-mcp-server'

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