browser_clipboard_write
Write text content to the system clipboard. Replaces any existing clipboard content. Useful for preparing content to paste into the browser.
When to use browser_clipboard_write
Use browser_clipboard_write when you need to automate a browser task. It is part of Owl Browser's Clipboard toolset and runs inside a self-hosted, source-level stealth engine, so every call inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Required
context_idstringrequiredThe unique identifier of the browser context (e.g., 'ctx_000001')
textstringrequiredText content to write to the system clipboard
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_clipboard_write do?
Write text content to the system clipboard. Replaces any existing clipboard content. Useful for preparing content to paste into the browser. It belongs to Owl Browser's Clipboard category and is available through the REST API, the Python SDK (browser.clipboard_write()), the Node.js SDK, and the MCP server.
What parameters does browser_clipboard_write accept?
browser_clipboard_write accepts 2 required parameters (context_id, text) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_clipboard_write.
Is browser_clipboard_write detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_clipboard_write executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.
Related Tools
browser_clipboard_readRead text content from the system clipboard. Returns the current clipboard text content. Useful for getting content that was copied from the browser.
browser_clipboard_clearClear the system clipboard content. Removes all text and data from the clipboard.
browser_clipboard_pastePaste the current clipboard text into the currently focused input, textarea, or contenteditable element on the page. Click the target field first to focus it, then paste. Fires a real paste event and updates framework-controlled inputs (React/Vue).
browser_create_contextCreate a new isolated browser context with its own cookies, storage, and optional proxy configuration. Each context acts as an independent browser session. Use this to create multiple isolated browsing sessions, configure proxy/Tor connections, load browser profiles with saved fingerprints, and enable/disable LLM features. Returns a context_id to use with other browser tools.
browser_navigateNavigate the browser to a specified URL. This is a non-blocking operation that starts navigation and returns immediately. Use browser_wait_for_network_idle or browser_wait_for_selector to wait for the page to fully load. Supports HTTP, HTTPS, file, and data URLs. When wait_until is set (load, networkidle, fullscroll, domcontentloaded) and the page declares WebMCP tools, the response includes a webmcp_tools array containing the full tool definitions (name, description, inputSchema). Use browser_webmcp_call_tool to execute any of these tools directly.
browser_observeAgent-native page observation. Returns the compacted OwlMark render (text-only structural view of the page), a handle table of interactive elements with stable tokens, page metadata, and a token estimate. Pass a handle token (e.g. 'b3') or 'pm:N' to browser_click/browser_type. Requires the context to be created with render_mode 'agent' or 'both'. ~20-100x fewer tokens than a screenshot for AI agent page understanding.