Tools
plungeai_executions
Browse your execution history: action list|get|output|conversation|files|delete|cancel|steer.
Authorizations
Authorization: Bearer ozk_….X-API-Key: ozk_….Every request needs a key, tools/list included.
Arguments
Maximum string length: 4000
Available options: list, get, output, conversation, delete, cancel, steer, files
for every action except `list`
Maximum string length: 256
Maximum string length: 256
for `steer`
Maximum string length: 65536
Default: 20
Required range: 1 <= x <= 100
Default: 0
Required range: 0 <= x <= 100000
text plus structuredContentAvailable options: markdown, json
Default: markdown
Output
Markdown text; format: "json" returns the same answer as a JSON document.
Browse your execution history: action list|get|output|conversation|files|delete|cancel|steer. cancel stops a running execution (cooperative — it stops at its next turn or tool boundary); steer (message) queues a message for a running one, delivered at its next turn; files lists the files the run wrote. Outputs are final user-ready markdown (tables, threads): show them to the user verbatim and complete — never summarize or re-type them.
Browse your execution history: action list, get, output, conversation, files, delete, cancel or steer. cancel stops a running execution cooperatively: it stops at its next turn or tool boundary. steer queues a message for a running execution, delivered at its next turn; files lists the files the run wrote. Outputs are final, user-ready Markdown (tables, threads): show them verbatim and complete, never summarize or re-type them.
Returns. list: # Executions (N), newest first (ID, Question, Workflow, Status, Source, When); JSON {"executions": [{id, input, workflow_name, status, start_time, duration, source}]}. get: the status answer of plungeai_get_workflow_status. output: the full result of plungeai_get_result. conversation: the follow-up thread; JSON {execution_id, messages}. cancel: Cancelling execution `<id>` — … (running runs only). steer: Queued your message to running execution `<id>` …, or an error when the run already finished (use plungeai_followup). files: a table of the files the run wrote. delete: Deleted execution `<id>`.; this cannot be undone. Details: 9.4 (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_executions","arguments":{"user_request":"show me my last 5 executions","action":"list","limit":5,"format":"json"}}}'Two parameters recur across the tools: user_request (on every tool: a string of up to 4,000 characters, optional; clients should always send it) and format (markdown by default, or json). Both are described once in Recurring parameters on the MCP overview.