Skip to main content
Glama

Browser Reload

browser_reload
Destructive

Use this to reload an identified Chromium tab, optionally bypassing cache. Reloading may lose unsaved form state; use a browser snapshot to verify the resulting page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "browser_reload"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWait for the page load event; default true.
titleNoChoose a page whose title contains this text.
deviceYesReMCP device id returned by list_devices. Required for every device operation.
endpointNoLoopback Chrome DevTools endpoint. Defaults to REMCP_CDP_URL or http://127.0.0.1:9222.
target_idNoPage target id returned by browser_tabs.
timeout_msNoTimeout in milliseconds.
ignore_cacheNoReload without cache when action=reload.
url_containsNoChoose a page whose URL contains this text.

Output Schema

NameRequiredDescriptionDefault
dataNoBrowser navigate structured result for browser_navigate. Stable fields are declared explicitly; platform-specific fields may be added. Large results may return truncated/bytes/preview instead of the full payload.
textYesConcise human-readable result of the tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false. The description adds useful behavioral context beyond that: reloading may lose unsaved form state, cache bypass is optional, and a snapshot should be used to verify the result.

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 two sentences and front-loads the core action before the risk warning. Every sentence adds useful information, and there is no filler.

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

Completeness4/5

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

For an eight-parameter browser mutation with full schema coverage, an output schema, and clear annotations, the description covers purpose, primary risk, cache behavior, and verification. Remaining gaps around selector precedence and alternatives are mitigated by the schema and sibling context.

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 coverage is 100%, so all eight parameters are already documented in the input schema. The description adds only high-level references to an identified tab and bypassing cache, without clarifying how target_id, title, and url_contains selectors interact.

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?

States a specific verb and resource: reload an identified Chromium tab, optionally bypassing cache. It is clear what the tool does, but it does not explicitly distinguish itself from nearby siblings such as browser_navigate_url or browser_back/browser_forward.

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

Usage Guidelines3/5

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

The description says to use this to reload a tab and recommends verifying with a browser snapshot afterward. However, it gives no explicit when-not guidance, prerequisites, or comparison to alternative navigation tools, so usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources