Skip to main content
Glama

browser_refresh

Refresh the current page in a browser instance to reload content and resolve display issues.

Instructions

Refresh the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceIdYesInstance ID

Implementation Reference

  • The handler function for the browser_refresh tool. It retrieves the browser instance, reloads the current page using page.reload(), and returns success with the new URL or an error.
    private async refresh(instanceId: string): Promise<ToolResult> {
      const instance = this.browserManager.getInstance(instanceId);
      if (!instance) {
        return { success: false, error: `Instance ${instanceId} not found` };
      }
    
      try {
        await instance.page.reload();
        return {
          success: true,
          data: { url: instance.page.url() },
          instanceId
        };
      } catch (error) {
        return {
          success: false,
          error: `Refresh failed: ${error instanceof Error ? error.message : error}`,
          instanceId
        };
      }
    }
  • src/tools.ts:150-163 (registration)
    The registration of the browser_refresh tool in the getTools() method, including name, description, and input schema requiring instanceId.
    {
      name: 'browser_refresh',
      description: 'Refresh the current page',
      inputSchema: {
        type: 'object',
        properties: {
          instanceId: {
            type: 'string',
            description: 'Instance ID'
          }
        },
        required: ['instanceId']
      }
    },
  • The input schema for browser_refresh tool, defining the required instanceId parameter.
    inputSchema: {
      type: 'object',
      properties: {
        instanceId: {
          type: 'string',
          description: 'Instance ID'
        }
      },
      required: ['instanceId']
    }
  • The switch case in executeTools that dispatches to the refresh handler for browser_refresh.
    case 'browser_refresh':
      return await this.refresh(args.instanceId);
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 for behavioral disclosure. 'Refresh the current page' implies a mutation (reloading), but it doesn't specify side effects (e.g., losing unsaved form data), authentication needs, rate limits, or what happens on failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior and risks.

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 is front-loaded with the core action ('Refresh') and immediately specifies the target ('the current page'), making it easy to parse. Every word earns its place, and there is no unnecessary elaboration or redundancy.

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 tool's complexity (a mutation with no annotations) and lack of output schema, the description is incomplete. It doesn't explain what 'refresh' entails (e.g., reloading, clearing cache), potential side effects, error conditions, or return values. For a browser interaction tool that could disrupt user state, this minimal description fails to provide adequate context for safe and effective use.

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%, with the single parameter 'instanceId' documented as 'Instance ID' in the schema. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 ('Refresh') and target ('the current page'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like browser_navigate or browser_go_back/forward, but the verb 'refresh' is specific enough to imply reloading the current page rather than navigation. This is better than vague or tautological descriptions.

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 prerequisites (e.g., needing an active browser instance), when not to use it (e.g., during form submission), or how it differs from siblings like browser_navigate (which loads a new URL) or browser_go_back/forward (which navigate history). Without such context, the agent must infer usage from the tool name alone.

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/sailaoda/concurrent-browser-mcp'

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