Module specs 

The tool surface: what a session is offered, transcribed from @playwright/mcp 0.0.83’s own tools/list - the capture preserved with the V1 spec.

Names and argument schemas are upstream’s, exactly, and so are the descriptions except the two named below. A prompt written against a Playwright MCP server names browser_navigate and passes a snapshot’s target ref, so a renamed tool or a moved argument is a prompt that resolves to something else. The additions this family carries beyond upstream are marked as such, and each names an argument upstream does not have - force, expression, the hand-off’s tab - or stands as a tool of its own built from the same driver. Two descriptions differ too: browser_snapshot gains the sentences on a ref’s lifetime and the route that fits a page still changing, neither of which upstream states, and browser_close’s is this family’s own, naming the session’s current tab because that is what a close means here.

Kept apart from the tools themselves so the surface a model reads is one table rather than a struct apiece: a shape is edited here and nowhere else.

Re-exports

use serde_json::Value; 🔒

use serde_json::json; 🔒

Structs

ToolSpec 🔒

One upstream tool: the name the model calls it by, the description it reads, and the argument schema the CLI validates against.

Functions

specs 🔒

The whole surface, in upstream’s own order.