browser_get_page_map
Get a compact structured map of all interactive elements on the page, grouped by sections. Returns a markdown table with numbered references, types, descriptions, current values, and selectors. Use element numbers as selectors in browser_click and browser_type (e.g., selector '5'). 10x cheaper than screenshots for AI agent page understanding.
When to use browser_get_page_map
Use browser_get_page_map when you need to inspect the state, attributes, and geometry of page elements. It is part of Owl Browser's Element State 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')
Optional
intentstringTask description to boost matching elements (e.g., 'buy nvidia jetson')
max_elementsintegerMaximum number of elements to return (0 = unlimited). Returns top N by importance score
regionstringFilter to specific page region: 'main', 'nav', 'header', 'footer', 'sidebar', 'article', 'form', 'dialog'. Empty = all regions
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_get_page_map do?
Get a compact structured map of all interactive elements on the page, grouped by sections. Returns a markdown table with numbered references, types, descriptions, current values, and selectors. Use element numbers as selectors in browser_click and browser_type (e.g., selector '5'). 10x cheaper than screenshots for AI agent page understanding. It belongs to Owl Browser's Element State category and is available through the REST API, the Python SDK (browser.get_page_map()), the Node.js SDK, and the MCP server.
What parameters does browser_get_page_map accept?
browser_get_page_map accepts 1 required parameter (context_id) and 3 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_get_page_map.
Is browser_get_page_map detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_get_page_map 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_is_visibleCheck if an element is visible on the page. Returns true if the element exists, is displayed (not hidden), and has non-zero dimensions. Useful for conditional logic based on visibility.
browser_is_enabledCheck if an element is enabled (not disabled). Returns true if the element doesn't have the 'disabled' attribute. Useful for checking if buttons, inputs, or other controls can be interacted with.
browser_is_checkedCheck if a checkbox or radio button is currently checked/selected. Returns true if the element has the 'checked' property set. Useful for verifying form state.
browser_is_editableCheck if an element is editable (not disabled AND not readOnly). Returns 'editable' if the element can accept user input, 'not_editable' if it is disabled or read-only. More comprehensive than browser_is_enabled which only checks the disabled attribute.
browser_count_elementsCount the number of elements matching a CSS selector. Returns the count as an integer. Useful for checking how many items exist (e.g., list items, search results, table rows) without extracting full element data.
browser_get_attributeGet the value of an HTML attribute from an element. Can retrieve any attribute including 'href', 'src', 'value', 'data-*' attributes, 'class', 'id', etc. Returns an empty string if the attribute doesn't exist or the element is not found.