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
{
  "listChanged": false
}

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

cred_listA

列出已保存的凭据(只有 handle/label/origin,没有密码)。

cred_fillA

把已保存的账号密码填进当前页面并可选提交。密码由本机凭据代理解密并注入,不会出现在返回值或模型上下文里。origin 必须与保存时绑定的一致。

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 browser action (navigate, click, type, hover, drag, screenshot), and paired tools like browser_network_requests/browser_network_request and browser_snapshot/browser_find are clearly differentiated by description. However, some boundaries blur: browser_evaluate vs browser_run_code_unsafe both execute JS, and browser_drop vs browser_drag both involve drag semantics, which could cause occasional misselection.

Naming Consistency4/5

Names follow a consistent snake_case browser_<verb|noun> pattern (browser_navigate, browser_click, browser_take_screenshot, browser_network_requests) with predictable prefixes. The only deviation is the two cred_* tools, which use a different domain prefix but still keep the same verb_noun style, so it remains readable.

Tool Count3/5

At 27 tools the set sits above the 25-tool 'heavy' threshold, and a few pairs (network_requests/network_request, evaluate/run_code_unsafe) could be consolidated. Still, browser automation is a genuinely broad domain where most tools earn their place, so it is heavy rather than bloated.

Completeness4/5

The surface covers the full browser lifecycle: navigation, element interaction, forms, tabs, dialogs, file upload, network/console inspection, snapshots, screenshots, media emulation, and credential filling. Minor gaps exist (no explicit cookie/storage-state management or download handling), but core workflows are well covered.