-
Notifications
You must be signed in to change notification settings - Fork 0
flow_schema
Kelly Ferrone edited this page Sep 12, 2026
·
1 revision
The shape of a flow document.
| MCP tool | flow_schema |
| HTTP | POST /flows/schema |
Every tool that may be a step and the parameters each takes, derived from the live tools — so it cannot describe a step that would not run.
This action takes no parameters.
An object.
| Status | Means |
|---|---|
400 |
The request cannot succeed as sent — an unusable name, a flow that does not exist, a document that would not run, or a write aimed at the read-only shared library. Do not retry it unchanged. |
401 |
Missing or wrong bearer token. |
500 |
Something failed that this server did not expect. |
Over MCP the same failures arrive as a tool error.
MCP
flow_schema()
HTTP
curl -X POST $SELENIUM_FLOW/flows/schema \
-H "Authorization: Bearer $TOKEN" \
-H 'Content-Type: application/json' \
-d '{
"session_id": "…"
}'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