Skip to main content
Glama
Sign In
invisible-playwright-mcp

invisible-playwright-mcp

by feder-cr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

browser_navigate

Navigate to a specified URL in the active browser tab, opening a new tab when none exists. Choose wait conditions to ensure page content is loaded before proceeding.

Instructions

Go to a url in the active tab, opening one if none exists.

wait_until is "domcontentloaded" by default, which returns as soon as the markup is parsed. Use "load" when the page needs its images and stylesheets, or "networkidle" for a single-page app that fetches its content after load.

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
urlYes
wait_untilNodomcontentloaded

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explains the default behavior of wait_until, the trade-offs among 'domcontentloaded', 'load', and 'networkidle', and the fact that a tab may be created if none exists. It does not mention timeouts or failure behavior, but the core side effects are disclosed.

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 compact and front-loaded. The first sentence states the action, and the second paragraph adds necessary parameter guidance without repetition or filler. Every sentence earns its place.

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?

The description provides sufficient context for an agent to invoke the tool correctly: the target resource, tab behavior, and wait_until semantics are covered. An output schema is present, so the lack of return-value detail is not a gap. Minor omissions like timeout handling prevent a perfect score.

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 schema provides 0% description coverage, so the description must compensate. It meaningfully explains the wait_until parameter and its options beyond the schema's bare default value. The url parameter is not elaborated, but its meaning is self-evident and the required format is implied by 'go to a url'.

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

Purpose5/5

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

The description uses a specific verb and resource: 'Go to a url in the active tab', which clearly states the tool's core function. It also distinguishes itself from sibling tools like session_new_page by noting it operates in the active tab and opens one only if none exists.

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 gives useful context about when to use different wait_until values, but it does not explicitly compare this tool to alternatives like session_new_page or browser_snapshot. The usage context is implied rather than stated as a decision rule between tools.

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