Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List workflows

list_workflows

Read-only

View workflows owned by your account, including status, trigger, version, and assigned agent. Filter by agent_id or use "none" to find unassigned workflows.

Instructions

List the workflows owned by the authenticated account, with each one's status, trigger, current version, and the agent that holds it (agent_id). Each workflow belongs to one agent — the one that built it — and that agent is the only one that can edit or run it from a chat. Pass agent_id to list just that agent's workflows, or agent_id="none" for the unassigned ones (created here or in the web app with no agent).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	No	Optional: a UUID of one of your agents to list only its workflows, or "none" for the unassigned ones.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`workflows`	Yes	Workflows visible to the authenticated account and optional agent filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Sep 19, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "workflows": {
+      "description": "Workflows visible to the authenticated account and optional agent filter.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "active_version": {
+            "maximum": 2147483647,
+            "minimum": -2147483648,
+            "type": [
+              "null",
+              "integer"
+            ]
+          },
+          "agent_deleted_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "agent_id": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "created_at": {
+            "type": "string"
+          },
+          "cron_expr": {
+            "type": "string"
+          },
+          "current_version": {
+            "maximum": 2147483647,
+            "minimum": -2147483648,
+            "type": "integer"
+          },
+          "description": {
+            "type": "string"
+          },
+          "engine": {
+            "type": "string"
+          },
+          "hook_key": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "next_fire_at": {
+            "type": [
+              "null",
+              "string"
+            ]
+          },
+          "notify_pref": {
+            "type": "string"
+          },
+          "paused_reason": {
+            "type": "string"
+          },
+          "spend_cap_month": {
+            "type": "integer"
+          },
+          "status": {
+            "type": "string"
+          },
+          "template_slug": {
+            "type": "string"
+          },
+          "trigger_kind": {
+            "type": "string"
+          },
+          "updated_at": {
+            "type": "string"
+          },
+          "user_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "user_id",
+          "agent_id",
+          "name",
+          "description",
+          "engine",
+          "status",
+          "current_version",
+          "active_version",
+          "trigger_kind",
+          "cron_expr",
+          "next_fire_at",
+          "hook_key",
+          "spend_cap_month",
+          "notify_pref",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "workflows"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.7.0Aug 9, 2026

addedInput schema / properties / agent_id

Added value: +{
+  "description": "Optional: a UUID of one of your agents to list only its workflows, or \"none\" for the unassigned ones.",
+  "type": "string"
+}

Changed1 schema field changedv0.3.0Jul 26, 2026
- addedInput schema / properties
```
Added value: +{}
```
Addedv0.1.1Jul 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds ownership/permission context beyond the annotations — each workflow belongs to one agent and only that agent can edit or run it — which materially affects interpretation of the results, though pagination and result-size behavior are unstated.

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?

Three front-loaded sentences that stay on topic: scope, ownership rule, then the filter. The agent_id filter is stated twice (narrative and sentinel form), which is mild redundancy but not padding.

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

Completeness5/5

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

Given one optional parameter, read-only annotations, and an existing output schema, the description covers everything an agent needs: what is listed, whose workflows, and how to filter. Return-value documentation is correctly left to the output schema.

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 parameter is fully documented there, including the "none" sentinel, so the baseline is 3. The description largely restates that same semantics rather than adding syntax or format detail.

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

Purpose5/5

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

States a specific verb+resource (list workflows) plus scope (owned by the authenticated account) and the fields returned (status, trigger, version, agent_id). An agent can distinguish it from list_agents and get_workflow immediately.

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

Usage Guidelines4/5

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

Explains how to narrow the result set with agent_id and the sentinel agent_id="none" for unassigned workflows, which is real when-to-use guidance. It does not name the sibling that serves single-workflow lookups (get_workflow), so it stops short of full alternative routing.

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