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

playwright-mcp-server

by doucej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

open_page

Navigate to a URL and wait for DOMContentLoaded before returning, ensuring the page is ready for subsequent actions.

Instructions

Navigate to a URL. Waits for DOMContentLoaded before returning.

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": "open_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute URL to navigate to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It adds one useful behavioral detail: 'Waits for DOMContentLoaded before returning.' However, it does not mention side effects like history changes, possible failures on invalid URLs, or any authentication needs, leaving gaps for a navigation tool.

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 short sentences: 'Navigate to a URL. Waits for DOMContentLoaded before returning.' Every word earns its place; there is no fluff or unnecessary detail.

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 a simple, single-parameter navigation tool, the description is quite complete. It discloses the key waiting behavior, and since there is no output schema, not explaining return values is acceptable. Minor omissions like error handling prevent a perfect score, but overall it gives enough context for an agent to use it correctly.

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 url parameter described as 'Absolute URL to navigate to.' The description adds no additional semantics beyond restating that it navigates to a URL, so the baseline score of 3 applies.

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 starts with 'Navigate to a URL', which is a specific verb plus resource. It clearly distinguishes this from sibling navigation tools like go_back, go_forward, and reload, which perform different navigation actions, and from get_url, which reads the current URL.

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

Usage Guidelines4/5

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

The description makes the use case clear: it is the tool for navigating to a new URL. While it does not explicitly name alternatives or state when not to use it, the context is unambiguous given the sibling names. It earns a 4 for clear context without exclusions.

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