chrome-use
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| chrome_use_openA | Navigate to a URL. Omitting |
| chrome_use_readB | Fetch a URL (or the active tab, if url is omitted) as agent-readable text/markdown. |
| chrome_use_snapshotB | Accessibility tree of the current page with @ref handles, for locating elements to click/fill/type. |
| chrome_use_clickB | Click an element (by CSS selector or @ref) or a raw viewport coordinate. Provide either |
| chrome_use_fillA | Clear and fill a form field (handles CodeMirror/Monaco/ProseMirror/contenteditable in addition to plain inputs). |
| chrome_use_typeC | Type text into an element (or, with no selector, whatever currently has focus). |
| chrome_use_pressC | Press a keyboard key (e.g. Enter, Tab, Control+a). |
| chrome_use_evalA | Run JavaScript in the page's main world (state persists, page handlers fire) and return its result. |
| chrome_use_waitA | Wait for an element, a fixed duration, a URL, a load state, a JS condition, text, or a download. Provide exactly one of: selector, ms, url, loadState, expression, text, download. |
| chrome_use_backB | Go back in browser history. |
| chrome_use_forwardB | Go forward in browser history. |
| chrome_use_reloadC | Reload the current page. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools are clearly distinct: open/read/snapshot/back/forward/reload each have a unique role, and click/fill/type/press target different interaction primitives. The only mild overlap is chrome_use_fill vs chrome_use_type (both insert text; fill clears first and handles rich editors), which descriptions clarify but an agent could still misselect in edge cases.
Every tool uses the identical chrome_use_<verb> pattern with short, action-oriented verbs (back, open, read, click, fill, type, press, eval, wait, forward, reload). No mixing of camelCase, casing, or verb styles across the set.
12 tools is squarely within the well-scoped range and each tool maps to a real browser-automation need (navigation, reading, element location, input, waiting). There is no obvious filler; the surface is compact yet covers the core loop of navigate-snapshot-act-wait.
The core automation lifecycle is covered: navigation, content reading, accessibility snapshotting, clicking/filling/typing/pressing, JS eval, and rich wait conditions. Gaps remain for tab/window management (list/new/close tabs), scrolling, dropdown selection, and screenshots, though most can be worked around via chrome_use_eval.