Playwright Tools for MCP - Browser automation server using Playwright for web testing and interaction
Playwright MCP has 11 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack consistent verb-noun structure (e.g., 'browser_close' vs 'browser_navigate'). Descriptions are minimal (10-30 chars), well below the 50-200 char LLM-optimized baseline. Most parameters lack descriptions entirely. No output schemas documented. Error handling is generic. The server reads like an early prototype rather than production-grade tooling.
Close the page
Returns all console messages
Upload one or multiple files
Install the browser specified in the config. Call this if you get an error about the browser not being installed.
Navigate to a URL
Go back to the previous page
Go forward to the next page
Descriptions are critically short (10-35 chars). LLM-optimized descriptions should be 50-200 chars explaining WHAT, WHEN, and any prerequisites. Current descriptions like 'Close the page' and 'Wait for a specified time in seconds' lack context for tool selection.
Most parameters lack descriptions. 'paths' in browser_file_upload has a description, but 'time' in browser_wait, 'width'/'height' in browser_resize, 'key' in browser_press_key, and 'url' in browser_navigate lack context. LLMs cannot infer parameter meaning from names alone.
No output schemas documented. Tools return ToolResult with content array, but LLMs cannot plan downstream calls without knowing what fields to expect. E.g., browser_console_messages should document the structure of console message objects returned.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Save page as PDF
Press a key on the keyboard
Resize the browser window
Wait for a specified time in seconds
Generic error handling. CallToolRequestSchema handler returns raw error strings without recovery guidance. Errors like 'Tool not found' or 'String(error)' give agents no actionable next steps. Should categorize errors as retryable, user-fixable, or fatal.
Tool naming inconsistency. 'browser_navigate' uses verb_noun, but 'browser_close', 'browser_wait', 'browser_resize' follow the same pattern. However, 'browser_console_messages' and 'browser_pdf_save' are noun-heavy. Standardize to verb_noun (e.g., 'get_console_messages', 'save_pdf').