Take a screenshot of the current browser page. Returns the file path to a saved PNG image. Screenshots are slow and heavy — prefer browser_get_dom and browser_get_page_info to understand page content and structure. Use screenshots only when you need to verify visual layout, debug rendering issues, or when DOM inspection is insufficient (e.g. canvas, images, charts). The response includes a pageRect describing which page-coordinate region the image depicts. To zoom into fine detail (especially after a full-page shot), call again with rect:{x,y,width,height} narrowed to a sub-region of that pageRect — coordinates are page CSS pixels.

Click on a page element. Specify by CSS selector, visible text, or x/y coordinates.

Type text into the focused element or a specific element.

Navigate to a URL in the current tab.

Scroll the page in a direction.

Get the page DOM structure. Returns interactive elements with their text, roles, and positions. This is the primary way to understand what is on the page — use it to find elements to click, read text content, and understand page layout. Faster and more detailed than screenshots.

Get current page metadata: URL, title, dimensions, scroll position. Use this to quickly check where you are and whether navigation succeeded — much faster than a screenshot.

Wait for a condition: element to appear, text to show, or fixed time.

Press a keyboard key, optionally with modifiers.

Execute JavaScript in the page context and return the result. Useful for extracting specific data, reading computed styles, or interacting with page APIs — often more precise than screenshots for getting exact values.

Ask the user to perform an action (e.g., sign in, solve CAPTCHA). AI pauses until user signals done.

Open a new browser tab.

List all open browser tabs in this session.

Switch to a specific browser tab by its ID.

Move mouse over an element to trigger hover effects.

Select an option from a dropdown element.

Create a new named tab group for a task. Use this to organize browsing by task — each group gets a label visible in Chrome. The new group becomes the active group; new tabs and navigations happen inside it.

Set a descriptive name for this browser session. The name appears on the Chrome tab group so the user can identify what task this session is working on. Call this early with a short task summary (e.g. "Search flights to Paris", "Debug login page").