Tools
plungeai_get_workflow_status
Check the status of one of your executions (self-heals stuck runs). Returns structured content too, including `continuation` when the run is paused awaiting user approval or an answer — relay that to the user and use plungeai_continue.
Authorizations
Authorization: Bearer ozk_….X-API-Key: ozk_….Every request needs a key, tools/list included.
Arguments
Maximum string length: 4000
Maximum string length: 256
Output
Check the status of one of your executions (it self-heals stuck runs). It also returns structured content, including continuation when the run is paused awaiting the user's approval or answer: relay that to the user and use plungeai_continue.
Returns. A Markdown status block and structuredContent with execution_id, status (running, completed, incomplete, failed, cancelled; incomplete only for async runs, since a sync call stamps its run ok, which then reads completed), error_message, workflow_name, started_at, duration_ms, final_task_id and continuation ({status, agent, question, pending_action} or null). A running row with a stored result is healed to completed; one with no heartbeat for more than 960 seconds is marked failed (Interrupted (run did not complete); the reason shows from the next read on). Details: 9.3 (opens in a new tab).
curl -s https://mcp.plungeai.com/v1 \
-H "Authorization: Bearer $PLUNGE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"plungeai_get_workflow_status","arguments":{"user_request":"is that still running?","execution_id":"<execution_id>"}}}'One parameter recurs across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it). It is described once in Recurring parameters on the MCP overview.