No user-submitted related servers found.
Scored across 31 tools
Most tools target distinct resource+action pairs (navigate, close, list, select, click, hover, fill, drag, upload, etc.). A few near-overlaps exist, such as get_firefox_info vs get_firefox_output and screenshot_page vs screencast_start, but their descriptions clarify the difference.
The dominant pattern is verb_noun, often with a by_uid suffix for element interactions (click_by_uid, hover_by_uid, etc.). Minor inconsistencies include list_pages vs new_page (plural vs singular) and the longer resolve_uid_to_selector, but the overall convention is clear.
At 31 tools, this exceeds the 25+ threshold for a heavy tool set. While many tools cover distinct features, several are auxiliary helpers (clear_snapshot, resolve_uid_to_selector, get_firefox_info) that could potentially be merged or removed without losing core functionality.
The tool surface covers a broad range of browser automation needs: page lifecycle, element interaction, snapshots, screenshots, downloads, dialogs, history, viewport control, extensions, screencasts, and script execution. Minor gaps exist (no explicit wait/condition, no direct text extraction, no iframe handling), but agents can generally work around them.