> ## Documentation Index
> Fetch the complete documentation index at: https://docs.plungeai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# plungeai_executions

> Browse your execution history: action list|get|output|conversation|delete|cancel.


Browse your execution history: action list|get|output|conversation|delete|cancel. `cancel` stops a running execution (cooperative — it stops at its next turn or tool boundary). 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`, `delete` or `cancel`. `cancel` stops a running execution cooperatively: it stops at its next turn or tool boundary. 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, When); JSON `{"executions": [{id, input, workflow_name, status, start_time, duration}]}`. `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). `delete`: ``Deleted execution `<id>`.``; this cannot be undone. Details: [9.4](https://mcp.plungeai.com/docs#94-run-history-plungeai_executions).

```bash
# verify
# expect: "executions"
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"}}}'
```

<Note>
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](/mcp-reference/overview#recurring-parameters) on the MCP overview.
</Note>

## Input schema

```json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "user_request": {
      "description": "The user's original request, verbatim and in their own words, before you translated it into this call. Always include it — the platform uses it for request context, routing and support diagnostics.",
      "type": "string",
      "maxLength": 4000
    },
    "action": {
      "type": "string",
      "enum": [
        "list",
        "get",
        "output",
        "conversation",
        "delete",
        "cancel"
      ]
    },
    "execution_id": {
      "type": "string",
      "maxLength": 256
    },
    "workflow_id": {
      "type": "string",
      "maxLength": 256
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "maximum": 100
    },
    "offset": {
      "type": "integer",
      "minimum": 0,
      "maximum": 100000
    },
    "format": {
      "default": "markdown",
      "description": "markdown (default): rendered for an AI reader · json: the same outcome as a JSON document in `text` plus `structuredContent`",
      "type": "string",
      "enum": [
        "markdown",
        "json"
      ]
    }
  },
  "required": [
    "action"
  ]
}
```