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

playwright-mcp-server

by doucej
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

load_state

Restore the last saved browser session by reloading persisted cookies and URL into a fresh browser instance.

Instructions

Reload the browser session from the last state saved on disk. Closes the current browser and opens a fresh one with the persisted cookies and URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "load_state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are present, so the description carries the full burden. It discloses the key behavioral trait that the current browser is closed and a fresh one is opened, which implies loss of unsaved state. This is useful, but it does not address prerequisites (e.g., an existing saved state) or error behavior.

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 concise sentences that are front-loaded with the core purpose, followed by a clear behavioral explanation. No superfluous content.

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 parameterless tool with no annotations or output schema, the description explains the main action and its effect on the browser. It could be more complete by mentioning what happens if no saved state exists, but overall it covers the essential information.

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 tool has zero parameters, so the baseline is 4. The description correctly focuses on the tool's behavior rather than parameter details.

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 (reload) and clearly defines the resource (browser session from a saved state on disk). It also explains the mechanism (closes current browser, opens fresh one with persisted cookies and URL), distinguishing it from related tools like reload or open_page.

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 provides implicit usage context: it is for restoring a previously saved session. However, it does not explicitly name alternative tools or state when not to use it, so it's clear but lacks exclusionary guidance.

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