Playwright Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| UV_PUBLISH_TOKEN | No | PyPI token for publishing the package | |
| UV_PUBLISH_PASSWORD | No | PyPI password for publishing the package | |
| UV_PUBLISH_USERNAME | No | PyPI username for publishing the package |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| playwright_navigateC | Navigate to a URL,thip op will auto create a session |
| playwright_screenshotC | Take a screenshot of the current page or a specific element |
| playwright_clickC | Click an element on the page using CSS selector |
| playwright_fillC | Fill out an input field |
| playwright_evaluateC | Execute JavaScript in the browser console |
| playwright_click_textB | Click an element on the page by its text content |
| playwright_get_text_contentB | Get the text content of all elements |
| playwright_get_html_contentC | Get the HTML content of the page |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, playwright_click targets elements by CSS selector while playwright_click_text uses text content, and tools like playwright_get_html_content versus playwright_get_text_content provide different types of content retrieval. The descriptions clearly differentiate the specific actions each tool performs.
All tools follow a consistent 'playwright_verb' pattern with snake_case throughout. The naming is perfectly predictable, starting with 'playwright_' followed by an action verb that accurately describes the tool's function, such as 'click', 'evaluate', 'fill', or 'navigate'.
With 8 tools, this server is well-scoped for browser automation tasks. Each tool earns its place by covering essential operations like navigation, interaction (clicking, filling), content retrieval (HTML, text), and utilities (screenshot, JavaScript execution). This count is ideal for the domain without being overwhelming or insufficient.
The toolset covers core browser automation workflows effectively, including navigation, element interaction, content extraction, and screenshots. Minor gaps exist, such as no explicit tool for waiting or handling alerts, but agents can work around these using existing tools like playwright_evaluate for JavaScript-based solutions. The surface is largely complete for the stated purpose.