Execution result by id

plungeai://executions/{id} · text/markdown · template

The stored result of one of your runs, by execution id (not the workflow id, Troubleshooting (opens in a new tab)). It reads the same stores as plungeai_get_result: the stored result, then the final task's output. The document looks like this:

# Execution <execution id>

- **Workflow:** `<workflow id>`

## Result

<the run's final output>

When there is no output, the Result section says why:

This resource gives the final result only. For one task's output, the full conversation thread, the "Steps in this run" index or a paused run's ⏸ block, use plungeai_get_result (Runs, results & follow-ups (opens in a new tab)). An unknown id, or one that is not yours, gets -32002 Execution not found: <id>.

# needs one of your execution ids — not auto-verified
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":13,"method":"resources/read","params":{"uri":"plungeai://executions/<execution id>"}}'

Result shape

resources/read answers one entry:

{
  "contents": [
    {
      "uri": "plungeai://executions/{id}",
      "mimeType": "text/markdown",
      "text": "…"
    }
  ]
}

Errors

resources/read answers JSON-RPC errors, not outcomes; the SDK prefixes each message with MCP error <code>: (resources/read).

• -32002 Execution not found: <id>: the execution is unknown or not yours.
• -32002 Resource not found: <uri>: the URI matches no resource or template.