-
Notifications
You must be signed in to change notification settings - Fork 0
extract
Kelly Ferrone edited this page Sep 9, 2026
·
7 revisions
Read an element's visible text and innerHTML.
| MCP tool | extract |
| HTTP | POST /browser/extract |
The primary way to read a page — prefer it over a screenshot, which costs far more. //body reads everything, but a narrower XPath keeps the result small.
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
xpath |
string | yes | — | |
session_id |
string | yes over HTTP | — | The session_id returned by /browser/open. Required here. |
url |
string | no | — | |
wait_timeout |
integer | no | 30 |
| Field | Type | Notes |
|---|---|---|
html |
string | innerHTML of the matched element. |
text |
string | Visible text of the element. |
url |
string | Current URL after the action. |
title |
string | Page title after the action. |
Errors are 400 for a bad argument, 401 without a token, 500 when the Grid
refuses. Over MCP the same failures arrive as a tool error.
MCP
extract(xpath="…")
HTTP
curl -X POST $SELENIUM_FLOW/browser/extract \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"session_id": "…",
"xpath": "…"
}'The action pages are generated from openapi.yaml, which is itself generated from the live MCP tool schemas — so they describe the server that shipped, not the one someone remembered. Prose belongs in wiki-notes/<tool>.md in the repo.
selenium-flow · MIT
Start here
Guides
Lifecycle
Going places
Doing things
Getting things out