Skip to main content
Glama
Sign In
BrowserMCP Extended

BrowserMCP Extended

by NEO10111
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_navigate

Navigate a Chrome or Chromium browser to a specified HTTP(S) URL, loading pages for automation, inspection, or testing.

Instructions

Navigate to a URL

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": {
      "url": "<url>"
    },
    "name": "browser_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTP(S) URL to navigate to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose whether navigation happens in the current tab or a new tab, whether it waits for page load, how long it waits, or whether it requires an existing browser session.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is appropriately terse for a simple action, though the terseness contributes to missing behavioral context.

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 navigation tool with no annotations and no output schema, the description is too minimal. An agent needs to know tab behavior, load-wait semantics, and failure modes; none of that context is present.

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?

The input schema fully documents the single url parameter with format guidance ("HTTP(S) URL"), and schema coverage is 100%. The description adds no parameter meaning beyond what the schema already provides, so the baseline is appropriate.

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 states a specific verb and resource ("Navigate to a URL"), making the core action clear. It does not differentiate from siblings such as browser_go_back, browser_go_forward, browser_reload, or browser_new_tab, which is a meaningful gap in a large browser toolset.

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?

There is no guidance on when to use this tool versus alternatives like browser_go_back, browser_reload, or browser_new_tab. The description offers no conditions, exclusions, or context for selection.

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

Deploy Server

Other Tools