Tools
plungeai_followup
Ask a follow-up about a completed execution (continues its agent session or researches with prior context). If the execution is still running, your message is queued and injected at its next turn (steer); if finished, it continues the conversation.
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
Maximum string length: 65536
Output
Markdown text.
Ask a follow-up about a completed execution: it continues the run's agent session, or researches with the prior context. If the execution is still running, the message is queued and injected at its next turn (steering); if it has finished, the conversation continues.
Returns. Running: Queued your message to running execution `<id>` (delivered at its next turn). Finished: the answer as Markdown, plus a ⏸ block if the agent pauses again. Errors (isError: true): Execution not found., Followup agent call failed, Failed to retrieve follow-up response. Details: 9.5 (opens in a new tab).
Runs a model and costs credits (not verified here):
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_followup","arguments":{"user_request":"now focus on the competitive landscape","execution_id":"<execution_id>","prompt":"Do the same analysis, but focus on the competitive landscape."}}}'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.