Skip to main content
Glama

campaignstack

by io.campaignstack
OverviewDiscussionsAdmin

Trigger workflow

campaignstack_trigger_workflow

Confirmed consequential execution: adds the selected leads to a workflow, or with no leadIds runs its sourcing now. A lead enters a workflow once: leads already in it, in any status, and leads an exclusion matches are skipped and counted in skipped. It joins the workflow queue and obeys pacing, review, account, and safety limits. To retry failed entries, use campaignstack_retry_workflow_entries.

Input Schema

NameRequiredDescriptionDefault
leadIdsNo
confirmedYesConfirms this starts workflow execution for real leads.
workflowIdYes
workspaceIdNoWorkspace 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

NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / confirmed / description
      Previous value: -"Confirms this starts or reruns workflow execution for real leads."New value: +"Confirms this starts workflow execution for real leads."
  2. Changed1 schema field changed
    • 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."
  3. Changed10 schema fields changed
    • 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"
+}
  4. Changed1 schema field changed
    • 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"
+}
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare non-readonly, non-destructive, open-world, non-idempotent, so the safety profile is partly covered. The description adds substantial context the annotations lack: one-time entry per lead, skip-and-count semantics, and that the run obeys pacing, review, account, and safety limits. It stops short of auth prerequisites or return shape.

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?

Four dense sentences that are front-loaded with the consequential-execution warning and mode selection, then semantics, then the sibling hand-off. Each sentence earns its place with no 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?

An output schema exists, so return values need not be described. For a 4-param mutation with full annotations, the description covers mode selection, skip semantics, queue/limit behavior, and the retry alternative, which is complete enough to invoke correctly.

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 description coverage is 50%, with leadIds and workflowId undocumented in the schema. The description compensates by defining leadIds behavior (present = add leads, absent = run sourcing) and reinforcing the confirmed gate, adding meaning beyond the bare 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?

States a specific verb and resource, and explicitly distinguishes its two modes: adds selected leads to a workflow, or with no leadIds runs its sourcing now. It names the retry sibling, so an agent can separate it from campaignstack_retry_workflow_entries without opening either schema.

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

Usage Guidelines5/5

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

Gives clear conditional usage: pass leadIds to enqueue leads, omit them to run sourcing. It explicitly routes retries to campaignstack_retry_workflow_entries and explains what happens to leads already present or matching an exclusion, leaving nothing to inference.

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

All campaignstack toolsInspect
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