Plori

Official

by plori-ai

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

List workflows

list_workflows

Read-only

Retrieve workflows owned by your account, showing status, trigger, version, and agent_id. Filter by agent_id to see only that agent's workflows or use 'none' for unassigned ones.

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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate that. It adds valuable behavioral context: each workflow is bound to a single agent who is the only one that can edit or run it from chat, and explains the 'none' semantics. This goes beyond the schema and annotations.

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?

The description is reasonably concise and front-loads the primary purpose and return fields. The ownership explanation is valuable and not excessive. It could be trimmed slightly, but it is well-structured and every sentence contributes.

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?

An output schema exists, so return values are already covered. The description covers key aspects: what is listed, the ownership constraint, and parameter usage. It does not mention pagination or ordering, but for a list tool with an output schema, that is a minor gap. Overall, it is sufficiently complete.

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

Parameters4/5

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

Schema coverage is 100% and the schema already documents agent_id. The description enriches the parameter by explaining the ownership model and the special 'none' case, giving an agent deeper understanding of the parameter's purpose beyond the raw schema.

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?

The description states the exact action ('list the workflows owned by the authenticated account') and enumerates the returned fields (status, trigger, current version, agent_id). It clearly distinguishes from sibling tools like list_runs and get_workflow by focusing on workflow ownership and listing behavior.

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?

It explains when to pass agent_id and the special 'none' value for unassigned workflows, and it mentions that each workflow belongs to one agent. It does not explicitly contrast with alternatives like get_workflow or list_workflow_executions, but the context is clear enough for an agent to decide when to use this tool.

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