Provide an accessible URL or HTML document, then choose a content review, screenshot, or PDF. For dynamic pages, specify the element that should be ready first.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Fetch rendered HTML and inspect its text for a focused content question.
/oo Browserless: Fetch rendered content for [page URL] with Browserless, waiting for selector [content selector] if needed. Summarize [content question] from the HTML and flag content that is missing.
Generate a screenshot and PDF from a supplied URL or HTML.
/oo Browserless: Use Browserless to capture [page URL] as a full-page screenshot and PDF with [PDF layout preferences]. Return both outputs for review.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Browserless API token.
Connect Browserless →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Browserless renders page content before returning HTML or a capture file. Rendered HTML supports text analysis, while screenshots and PDFs preserve the page for review.
Render a URL or supplied HTML and retrieve the resulting HTML, with optional wait conditions.
Create screenshots or PDFs with capture and layout options.
Fetch fully rendered HTML content from Browserless.
Leina 
Wanta 
browserless.fetch_content Generate a Browserless screenshot and return it as base64 content.
browserless.take_screenshot Generate a Browserless PDF file and return it as base64 content.
browserless.generate_pdf No matching tools.
Provide one of them per request. A URL captures an accessible page; supplied HTML captures that document.
Yes. Specify a selector, event, or wait interval appropriate for the page before fetching or capturing it.
Yes. They are separate capture operations; specify the page and desired PDF layout.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.