-
Notifications
You must be signed in to change notification settings - Fork 0
write
Type text into an input, textarea or contenteditable.
| MCP tool | write |
| HTTP | POST /browser/write |
Set submit to press Enter afterwards, which fills and submits a search box in one call. Returns the field's value read back off the element, so you can confirm the text actually landed.
Address the field with EITHER xpath OR css, never both and never neither.
| Name | Type | Required | Default | Notes |
|---|---|---|---|---|
text |
string | yes | — | |
xpath |
string | no | — | |
css |
string | no | — | |
session_id |
string | yes over HTTP | — | The session_id returned by /browser/open. Required here. |
url |
string | no | — | |
clear |
boolean | no | true |
|
submit |
boolean | no | false |
|
wait_timeout |
integer | no | 30 |
| Field | Type | Notes |
|---|---|---|
value |
string | The field's value read back off the element, so a caller can confirm the text landed. |
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
write(text="…")
HTTP
curl -X POST $SELENIUM_FLOW/browser/write \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"session_id": "…",
"text": "…"
}'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
Lifecycle
Going places
Doing things
Getting things out