browser_get_downloads
List all downloads for the context with their current status. Returns download ID, filename, URL, progress percentage, bytes downloaded, total size, and state (pending, in_progress, completed, failed, cancelled).
When to use browser_get_downloads
Use browser_get_downloads when you need to manage file downloads triggered by a page. It is part of Owl Browser's Download Management 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')
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_get_downloads do?
List all downloads for the context with their current status. Returns download ID, filename, URL, progress percentage, bytes downloaded, total size, and state (pending, in_progress, completed, failed, cancelled). It belongs to Owl Browser's Download Management category and is available through the REST API, the Python SDK (browser.get_downloads()), the Node.js SDK, and the MCP server.
What parameters does browser_get_downloads accept?
browser_get_downloads accepts 1 required parameter (context_id) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_get_downloads.
Is browser_get_downloads detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_get_downloads 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_set_download_pathConfigure the directory where browser downloads will be saved. Must be set before triggering downloads. The directory must exist and be writable. Downloaded files are saved with their original filenames.
browser_get_active_downloadsGet only currently active (in-progress) downloads for the context. More efficient than get_downloads when you only need to monitor ongoing transfers.
browser_cancel_downloadCancel an in-progress download. Stops the download immediately and may delete partially downloaded content. The download will be marked as 'cancelled' in the downloads list.
http_downloadDownload a file from an HTTP/HTTPS URL and save it to disk. Supports resume for interrupted downloads, custom output paths, proxy configuration, and Tor anonymization. If no output path is specified, the file is saved to /tmp/owl_downloads/ with a filename derived from the URL or Content-Disposition header. Returns the file path, size, content type, and download timing.
ftp_downloadDownload a file from an FTP server. Supports authenticated FTP, FTPS (FTP over SSL/TLS), proxy configuration, and Tor anonymization. If no output path is specified, saves to /tmp/owl_downloads/. Returns file path, size, and download timing.
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.