browser_get_element_at_position
Get detailed information about the DOM element at specific XY coordinates. Returns element tag, ID, classes, bounding box, text content, and computed styles. Use with browser_show_grid_overlay to find coordinates. Useful for debugging and building element picker UIs.
When to use browser_get_element_at_position
Use browser_get_element_at_position 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')
xnumberrequiredX coordinate in pixels from the left edge of the viewport. Use browser_show_grid_overlay to visualize coordinates on the page
ynumberrequiredY coordinate in pixels from the top edge of the viewport. Use browser_show_grid_overlay to visualize coordinates on the page
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_get_element_at_position do?
Get detailed information about the DOM element at specific XY coordinates. Returns element tag, ID, classes, bounding box, text content, and computed styles. Use with browser_show_grid_overlay to find coordinates. Useful for debugging and building element picker UIs. It belongs to Owl Browser's Element State category and is available through the REST API, the Python SDK (browser.get_element_at_position()), the Node.js SDK, and the MCP server.
What parameters does browser_get_element_at_position accept?
browser_get_element_at_position accepts 3 required parameters (context_id, x, y) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_get_element_at_position.
Is browser_get_element_at_position detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_get_element_at_position 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.