Skip to main content
Glama

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
browser_closeB

Close the page

browser_resizeB

Resize the browser window

browser_console_messagesC

Returns all console messages

browser_handle_dialogC

Handle a dialog

browser_emulate_mediaA

Emulate CSS media features for the page, for example switch between the light and dark color scheme. Omitted parameters are left unchanged; null clears an override.

browser_evaluateC

Evaluate JavaScript expression on page or element

browser_file_uploadB

Upload one or multiple files

browser_dropA

Drop files or MIME-typed data onto an element, as if dragged from outside the page. At least one of "paths" or "data" must be provided.

browser_findA

Search the accessibility snapshot of the current page for text or a regular expression. Returns matching snapshot nodes with a few lines of surrounding context (like search snippets), each shown under its path from the root of the tree, which is cheaper than capturing the whole snapshot when you only need to locate an element and its ref.

browser_fill_formB

Fill multiple form fields

browser_press_keyB

Press a key on the keyboard

browser_typeB

Type text into editable element

browser_navigateC

Navigate to a URL

browser_navigate_backA

Go back to the previous page in the history

browser_network_requestsA

Returns a numbered list of network requests since loading the page. Use browser_network_request with the number to get full details.

browser_network_requestA

Returns full details (headers and body) of a single network request, or a single part if part is set. Use the number from browser_network_requests.

browser_run_code_unsafeA

Run a Playwright code snippet. Unsafe: executes arbitrary JavaScript in the Playwright server process and is RCE-equivalent.

browser_take_screenshotA

Take a screenshot of the current page. You can't perform actions based on the screenshot, use browser_snapshot for actions.

browser_snapshotA

Capture accessibility snapshot of the current page, this is better than screenshot

browser_clickB

Perform click on a web page

browser_dragA

Perform drag and drop between two elements

browser_hoverA

Hover over element on page

browser_select_optionB

Select an option in a dropdown

browser_tabsA

List, create, close, or select a browser tab.

browser_wait_forB

Wait for text to appear or disappear or a specified time to pass

snapshot_detailA

Read part of the last page snapshot that tokensave-mcp-diet shortened. Pass ref (an element ref or uid from the outline, e.g. e123 or 1_45) to get that element and everything inside it, or query to find text on the page with its surrounding section. Use this instead of taking a new full snapshot.

result_detailA

Read part of a long tool result that tokensave-mcp-diet shortened (script output, logs, dumps). Pass id from the note (e.g. r1), and lines (e.g. "200-260") or query (text to find). Prefer this over running the command again.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 27 tools

Disambiguation4/5

Most tools map to a distinct action (navigate, click, type, hover, select_option, wait_for, resize, close) and the descriptions actively steer choices, e.g. snapshot vs screenshot vs find vs snapshot_detail. A few boundaries blur: browser_evaluate vs browser_run_code_unsafe both execute JS, browser_drag vs browser_drop both involve dragging, and browser_snapshot vs browser_find vs snapshot_detail all read page structure.

Naming Consistency4/5

The set is overwhelmingly snake_case with a uniform browser_ prefix and a consistent verb_noun shape (browser_press_key, browser_navigate_back, browser_select_option). Deviations are minor: noun-only names like browser_snapshot and browser_tabs, and the two tokensave helper tools (snapshot_detail, result_detail) drop the browser_ prefix entirely.

Tool Count3/5

27 tools is heavy for a single server, though browser automation is a genuinely broad domain and nearly every tool covers a real capability. Some consolidation is possible (evaluate/run_code_unsafe, drag/drop, snapshot/find/snapshot_detail), so the surface sits above the comfortable range rather than clearly over-scoped.

Completeness4/5

Coverage is strong across the browser lifecycle: navigation, element interaction, form filling, file upload, drag/drop, dialogs, tabs, viewport, console, network inspection, media emulation, plus result-truncation helpers. Gaps are modest—no cookie/localStorage or session-state tools, no request interception, and scrolling must be done indirectly via evaluate or key presses.

Maintenance

ActivityMaintained
ResponsivenessNo issues