Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List workflow executions

list_workflow_executions

Read-only

Retrieve a workflow's recent executions, newest first, to review status, fault cause, billing, trigger source, timing, credits, and timestamps.

Instructions

List a workflow's recent executions, most recent first. Each record includes status, fault, billing, trigger source, timing, credits, and timestamps. fault explains why a non-succeeded execution ended. user means the workflow's own steps or limits. A platform fault is never billed. fault is null when the execution succeeded. billed is the billing flag.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`workflow_id`	Yes	The workflow's UUID (from list_workflows or create_workflow).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`executions`	Yes	Recent workflow executions, most recent first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "executions": {
+      "description": "Recent workflow executions, most recent first.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "billed": {
+            "description": "The billing flag. True only for a user-fault succeeded, failed, or timed-out execution.",
+            "type": "boolean"
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "credits": {
+            "type": [
+              "null",
+              "integer"
+            ]
+          },
+          "duration_ms": {
+            "type": [
+              "null",
+              "integer"
+            ]
+          },
+          "ended_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "error": {
+            "description": "Arbitrary JSON owned by the producing engine."
+          },
+          "fault": {
+            "description": "Why a non-succeeded execution ended. User means the workflow's own steps or limits. A platform fault is never billed. This field is null when the execution succeeded.",
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "started_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "step_stats": {
+            "description": "Arbitrary JSON owned by the producing engine."
+          },
+          "steps": {
+            "description": "Arbitrary JSON owned by the producing engine."
+          },
+          "trigger_source": {
+            "type": "string"
+          },
+          "workflow_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "workflow_id",
+          "status",
+          "fault",
+          "billed",
+          "trigger_source",
+          "started_at",
+          "ended_at",
+          "duration_ms",
+          "credits",
+          "created_at"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "executions"
+  ],
+  "type": "object"
+}

Addedv0.7.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so the safety profile is covered. The description adds useful domain semantics ('a platform fault is never billed', 'fault is null when the execution succeeded'), but those are return-field semantics that the existing output schema should carry, and it discloses no operational traits such as result caps, ordering guarantees, or auth requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action and ordering, then short field notes. A few sentences approach tautology ('billed is the billing flag'), which is minor waste but keeps the whole description compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with full schema coverage and an output schema, an agent has what it needs to invoke it. The remaining gap is only the absence of any statement about how many executions are returned or how to page.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single workflow_id parameter is fully documented in the schema (UUID from list_workflows or create_workflow). The description adds nothing about the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource with scope ('a workflow's recent executions') and ordering ('most recent first'), which separates it from the single-record get_workflow_execution sibling. It does not, however, explicitly contrast itself with list_runs or other list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no exclusions, and no routing to get_workflow_execution for a single execution or to list_runs for a different resource. The 'recent' wording implies a bounded default list but never states a limit or pagination behavior.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.