campaignstack

campaignstack_get_craft_config_tree

Read-onlyIdempotent

Everything a craft prompt is built from, in one read: the workspace's five playbook sections with their caps, offerContext, capabilities and outreach intents; every campaign's guidance, offer addendum and intents; every workflow's craft nodes with the text a human wrote into them; every signal agent's script; and one voice profile summary per person and language. It also returns warnings: tone language in an agent script, a section written as an explanation of itself, the same sentence sitting at two levels, a campaign goal promising something the offer never states, a greeting that is really a whole message, a voice built on almost no real writing. Each warning names the tool and field that fixes it. Call this before editing craft configuration, or when the user asks to change how CampaignStack writes messages. It does not show one node's actual rendered prompt: campaignstack_preview_craft_prompt does that for a specific lead. Exemplars and message bodies are never returned.

Input Schema

TableJSON Schema

Name	Required	Description
`include`	No	Subtrees to return. Default: all five.
`campaignId`	No	Narrow campaigns and their workflows to this one campaign.
`workspaceId`	No	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.
`resolveForWorkflowId`	No	Also return what THIS workflow resolves to: which intent level wins, which sections its scope is sent, and the campaign guidance and offer addendum it carries.
`resolveForSignalAgentId`	No	Same, for a signal agent. An agent resolves workflow then workspace and never sees a campaign's guidance or intents.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`voice`	No
`warnings`	No
`campaigns`	No
`workflows`	No
`workspace`	No
`signalAgents`	No
`resolvedForWorkflow`	No
`resolvedForSignalAgent`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "campaigns": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "resolvedForSignalAgent": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {}
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "resolvedForWorkflow": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {}
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "signalAgents": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "voice": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "warnings": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workflows": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {
+              "items": {},
+              "type": "array"
+            }
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "workspace": {
+      "anyOf": [
+        {
+          "anyOf": [
+            {
+              "not": {}
+            },
+            {}
+          ]
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

AddedSep 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds substantial behavioral detail beyond that: it lists the types of warnings returned (tone language, self-referential sections, duplicate sentences, etc.), notes that each warning names the fixing tool and field, and explicitly states what is never returned (exemplars and message bodies). This adds rich context about side effects and return contents without contradicting the annotations.

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?

Though lengthy, every sentence earns its place. It front-loads the core content (what is returned), then details warnings, then usage guidance, then explicit exclusions. The structure is logical and scannable, with no redundant filler.

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 the tool's complexity (five subtrees, multiple resolution modes, warnings), the description is thorough: it covers what is included, what warnings are emitted, when to use it, and what it deliberately does not return. Since an output schema exists, return-value details are handled there. Nothing an agent needs to decide when to call and what to expect is missing.

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 100% – every parameter has a description that fully explains its purpose (include, campaignId, workspaceId, resolveForWorkflowId, resolveForSignalAgentId). The tool description adds no extra parameter-level semantics beyond what the schema already provides, but it does contextualize the overall read behavior. Since the schema carries the burden, baseline 3 is appropriate.

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 a specific verb and resource: 'get_craft_config_tree' returns the entire craft configuration in one read, enumerating exactly which sections are included (workspace playbook, campaigns, workflows, signal agents, voice). It clearly distinguishes itself from the sibling preview_craft_prompt by stating what it does not return (rendered prompt, exemplars, message bodies). This leaves no ambiguity about the tool's purpose.

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?

Explicitly says when to call: 'Call this before editing craft configuration, or when the user asks to change how CampaignStack writes messages.' It also states what it does not do and points to the alternative: 'It does not show one node's actual rendered prompt: campaignstack_preview_craft_prompt does that for a specific lead.' This gives clear when/when-not and alternative guidance.

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?