campaignstack

Craft message

campaignstack_craft_message

Draft one outbound message without sending anything. Select channel linkedin/email and kind first_touch, connection_note, comment, comment_reply, followup, or meeting_followup. Returns sent:false; callers must read the draft back and use a separate send/action tool only after explicit approval. It never books a meeting for you: when a follow-up finds the lead accepted a time offered earlier, schedulingAcceptance names it (booked:false) for a person to book.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`leadId`	No
`channel`	Yes	Draft channel. LinkedIn drafts do not send; email drafts do not send.
`newEndAt`	No
`template`	No
`accountId`	No	LinkedIn account that will send the draft: names the speaker and picks the voice on every LinkedIn kind. Required for a LinkedIn follow-up, where it also reads the thread.
`meetingId`	No	Required for kind=meeting_followup.
`campaignId`	No
`newStartAt`	No
`workflowId`	No
`commentText`	No
`meetingKind`	No
`postContent`	No
`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.
`instructions`	No
`conversationMessages`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / accountId / description

Previous value: -"LinkedIn account for follow-up thread context."New value: +"LinkedIn account that will send the draft: names the speaker and picks the voice on every LinkedIn kind. Required for a LinkedIn follow-up, where it also reads the thread."

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."

Changed22 schema fields changedSep 26, 2026

addedInput schema / properties / accountId

Added value: +{
+  "description": "LinkedIn account for follow-up thread context.",
+  "type": "string"
+}

addedInput schema / properties / channel

Added value: +{
+  "description": "Draft channel. LinkedIn drafts do not send; email drafts do not send.",
+  "enum": [
+    "linkedin",
+    "email"
+  ],
+  "type": "string"
+}

addedInput schema / properties / commentText
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / conversationMessages

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "sender": {
+        "enum": [
+          "self",
+          "lead"
+        ],
+        "type": "string"
+      },
+      "text": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "sender",
+      "text"
+    ],
+    "type": "object"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

addedInput schema / properties / instructions / maxLength
```
Added value: +4000
```

addedInput schema / properties / kind

Added value: +{
+  "enum": [
+    "first_touch",
+    "connection_note",
+    "comment",
+    "comment_reply",
+    "followup",
+    "meeting_followup"
+  ],
+  "type": "string"
+}

removedInput schema / properties / leadId / minLength
```
Removed value: -1
```

addedInput schema / properties / meetingId

Added value: +{
+  "description": "Required for kind=meeting_followup.",
+  "type": "string"
+}

addedInput schema / properties / meetingKind

Added value: +{
+  "enum": [
+    "reschedule",
+    "no_show",
+    "cancelled"
+  ],
+  "type": "string"
+}

removedInput schema / properties / messageTemplate
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / newEndAt
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / newStartAt
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / postContent
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / template

Added value: +{
+  "maxLength": 4000,
+  "type": "string"
+}

removedInput schema / properties / workflowId / description

Removed value: -"Workflow the craft belongs to. Used to resolve signal-agent playbooks. Injected automatically for runner agents."

changedInput schema / required

Previous value: -[
-  "leadId"
-]New value: +[
+  "channel",
+  "kind"
+]

removedOutput schema / properties / messageText

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

removedOutput schema / properties / needsHumanReview

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

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

addedOutput schema / properties / results

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

removedOutput schema / properties / reviewReason

Removed value: -{
-  "anyOf": [
-    {
-      "anyOf": [
-        {
-          "not": {}
-        },
-        {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      ]
-    },
-    {
-      "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": {
+    "messageText": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "string"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "needsHumanReview": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": "boolean"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "reviewReason": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed9 schema fields changedSep 14, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / campaignId
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / instructions
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / leadId

Added value: +{
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / messageTemplate
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / workflowId

Added value: +{
+  "description": "Workflow the craft belongs to. Used to resolve signal-agent playbooks. Injected automatically for runner agents.",
+  "type": "string"
+}

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"
+}

addedInput schema / required
```
Added value: +[
+  "leadId"
+]
```

First observedSep 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: sent:false is returned, sending and booking are deliberately out of scope, and schedulingAcceptance with booked:false is surfaced when a follow-up discovers a prior accepted time. That said, it does not say whether drafts persist or overwrite, nor anything about idempotency, for a tool whose annotations show a non-read-only mutation.

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 with no filler; the no-send constraint and the approval gate come first. Slightly dense with domain-specific terms (schedulingAcceptance, booked:false) that assume prior context.

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

Completeness3/5

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

The output schema means return values need no explanation, and the safety/approval story is well covered. However, for a 16-parameter tool with 25% schema coverage, many inputs remain opaque, so an agent can understand the intent but not reliably populate all arguments.

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

Parameters2/5

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

Schema coverage is only 25% across 16 parameters, so most inputs (leadId, template, instructions, conversationMessages, campaignId, workflowId, commentText, postContent, meetingKind, the reschedule timestamps) are explained nowhere. The description largely restates the already-documented channel and kind enums, so it does not compensate for the coverage gap.

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 (draft one outbound message) and immediately bounds it (without sending anything), which cleanly separates it from siblings like campaignstack_send_message or campaignstack_comment_on_post.

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?

Tells the agent when this applies (drafting, not sending) and what must follow (read the draft back, then call a separate send/action tool only after explicit approval). It never names the specific sibling send tool, so routing still requires a lookup, but the workflow intent is explicit.

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?