No user-submitted related servers found.
Scored across 23 tools
Most tools target clearly distinct actions (click, hover, navigate, screenshot), and descriptions help distinguish close pairs like snapshot vs. screenshot and network_requests vs. network_request. However, several clusters overlap—type/fill_form/press_key, drag/drop/file_upload, and evaluate/run_code_unsafe—which could occasionally cause misselection.
All 23 tools use a consistent browser_ prefix with snake_case, making the set predictable and easy to scan. The pattern mixes verb-based and noun-based names (browser_click vs. browser_snapshot), but the convention itself is stable throughout.
23 tools is slightly heavy for the typical 3-15 range, but each maps to a distinct Playwright action needed for full browser automation. There is no obvious redundancy, though a few tools (drop vs. drag, evaluate vs. run_code_unsafe) could potentially be consolidated.
The surface covers navigation, interaction, forms, dialogs, network inspection, screenshots/snapshots, tabs, and waits—a comprehensive lifecycle for browser automation. Minor gaps include no forward-navigation counterpart to browser_navigate_back and no explicit scroll tool, though browser_evaluate can work around both.