Skip to main content
Glama
devqa07

Playwright Automation MCP Server

by devqa07

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
navigate_to_automation_exerciseA

Navigate to the AutomationExercise website homepage

register_new_userB

Register a new user account on AutomationExercise with full details

login_userB

Login to an existing user account on AutomationExercise

browse_productsB

Browse products on AutomationExercise, optionally by category

add_product_to_cartB

Add a specific product to the shopping cart

view_cartA

View the contents of the shopping cart

take_screenshotB

Take a screenshot of the current page

click_continueA

Click the Continue button after successful registration

logout_userA

Logout the currently logged in user

close_browserA

Close the browser and cleanup resources

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a distinct action: navigation, login, registration, product browsing, cart management, screenshot, logout, and browser cleanup. No two tools appear to do the same thing, even though click_continue is narrow but clearly tied to the registration flow.

Naming Consistency5/5

All tools use snake_case with a clear verb-first pattern (e.g., login_user, browse_products, add_product_to_cart). Naming is highly consistent and predictable, with no camelCase or mixing of conventions.

Tool Count5/5

Ten tools is a well-scoped set for automating a specific website's user flows. Each tool serves a concrete purpose in the main journey (navigate, register, login, browse, cart, logout), with no bloat or unnecessary duplication.

Completeness4/5

The tool set covers the core lifecycle of a user on AutomationExercise: registration, login, browsing, adding to cart, viewing cart, and logout. Minor gaps exist, such as no checkout, cart removal, or product detail retrieval, but these are not critical for the apparent automation purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues