campaignstack

Trigger workflow

campaignstack_trigger_workflow

Confirmed consequential execution: starts or reruns a workflow for selected leads or its source list. It joins the workflow queue and obeys pacing, review, account, and safety limits.

Input Schema

TableJSON Schema

Name	Required	Description
`leadIds`	No
`confirmed`	Yes	Confirms this starts or reruns workflow execution for real leads.
`workflowId`	Yes
`workspaceId`	No	Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`results`	No
`warnings`	No
`workflowId`	No
`workspaceId`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / workspaceId / description

Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."

Changed10 schema fields changedSep 26, 2026

addedInput schema / properties / confirmed

Added value: +{
+  "const": true,
+  "description": "Confirms this starts or reruns workflow execution for real leads.",
+  "type": "boolean"
+}

addedInput schema / properties / workspaceId

Added value: +{
+  "description": "Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "workflowId"
-]New value: +[
+  "workflowId",
+  "confirmed"
+]

addedOutput schema / properties / ok
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / results

Added value: +{
+  "items": {},
+  "type": "array"
+}

removedOutput schema / properties / triggered

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": "number"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / warnings

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / workflowId
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / workflowStatus

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": "string"
-        }
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / workspaceId
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "triggered": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "number"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workflowStatus": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false). The description goes further, disclosing that execution joins a workflow queue and is subject to pacing, review, account, and safety limits — real behavioral context that explains why a trigger may not fire immediately.

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

Conciseness5/5

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

Two sentences, and the consequence/confirmation warning is front-loaded before the mechanics. No filler; every clause carries information.

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 need not be described, and annotations carry the safety profile. The description covers the queued, rate-limited nature of the trigger, an important operational trait; the only real gap is not routing the agent away from the near-sibling retry tools.

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 coverage is 50%; workflowId and leadIds have no schema descriptions. The description partly compensates by clarifying that leads are optional ('selected leads or its source list'), but adds nothing about workflowId format or the 100-item leadIds cap. Baseline 3 is right when the schema and description together leave gaps.

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 pair (starts or reruns) and resource (a workflow), plus the scope it acts on ('selected leads or its source list'). This is enough to separate it from siblings like get_workflows or diagnose_workflow_sourcing, though it never explicitly names the closest alternative, retry_workflow_entries.

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

Usage Guidelines3/5

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

'Confirmed consequential execution' signals that confirmation is required before invoking, which is implied usage guidance. However, it gives no condition for choosing this over retry_workflow_entries (rerun of failures) or retry_workflow_entries/cancel_workflow_node_leads, so the when-not guidance is absent.

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

All campaignstack tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?