Scribe Mail

Create a marketing campaign

create_marketing_campaign

Create a marketing campaign. name, start_time, end_time, and time_zone are required; a missing one returns 422. The campaign is created as a draft — use schedule_marketing_campaign to activate it. content is a block tree (a stack root whose children are blocks) strict-validated server-side, the same format as signature draft_content; smart_fields_conditions and signature_template_ids set the targeting.

Input Schema

Name	Required	Description
`name`	Yes	Campaign name (required).
`content`	No	Campaign block tree (ILayoutBlock): a `stack` root whose `children` are blocks. Strict-validated server-side. Omit to leave unchanged; null to clear. Every node (block AND token) needs an `id` that is a fresh LOWERCASE uuid — any other string, including an uppercase uuid, is rejected 422. Every numeric size is in PIXELS, never a CSS multiplier: `lineHeight` is a px line box (~1.3x fontSize, e.g. fontSize 14 -> 18), so 1.3 is rejected. Call get_content_schema for the full schema, every enum value, and a worked example.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`end_time`	Yes	ISO-8601 end of the campaign window (required).
`behaviour`	No	How the campaign content combines with the signature (replace or append).
`time_zone`	Yes	IANA time zone, e.g. 'Europe/Paris' (required).
`send_email`	No
`start_time`	Yes	ISO-8601 start of the campaign window (required).
`filter_kind`	No	Which targeting dimension applies: by signature_templates or by smart_fields conditions.
`signature_template_ids`	No	UUIDs of the signature templates to apply the campaign to (replaces the set; [] clears).
`smart_fields_conditions`	No	Smart-field targeting: an array of OR-groups, each an array of AND-conditions { smart_field_id (uuid), operator, values }.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

addedOutput schema / properties / data / properties / name / description

Added value: +"Campaign name. Null for a legacy draft that was saved without one. Report it as an unnamed draft and refer to it by its id rather than inventing a name."

changedOutput schema / properties / data / properties / name / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed7 schema fields changedOct 28, 2026

changedInput schema / properties / content / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "blockStyle": {
-        "additionalProperties": {},
-        "propertyNames": {
-          "type": "string"
-        },
-        "type": "object"
-      },
-      "children": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "id": {
-              "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
-              "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
-              "type": "string"
-            },
-            "role": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "type": {
-              "enum": [
-                "stack",
-                "text",
-                "image",
-                "icon",
-                "list",
-                "listItem",
-                "listItemLabel",
-                "socialList",
-                "socialListItem",
-                "button",
-                "divider",
-                "marketing"
-              ],
-              "type": "string"
-            },
-            "visible": {
-              "type": "boolean"
-            }
-          },
-          "required": [
-            "id",
-            "type",
-            "role",
-            "visible"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "id": {
-        "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
-        "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
-        "type": "string"
-      },
-      "role": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "type": {
-        "const": "stack",
-        "type": "string"
-      },
-      "visible": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "id",
-      "type",
-      "role",
-      "visible",
-      "blockStyle",
-      "children"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "blockStyle": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "children": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "id": {
+              "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
+              "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
+              "type": "string"
+            },
+            "role": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "enum": [
+                "stack",
+                "text",
+                "image",
+                "icon",
+                "list",
+                "listItem",
+                "listItemLabel",
+                "socialList",
+                "socialListItem",
+                "button",
+                "divider",
+                "marketing"
+              ],
+              "type": "string"
+            },
+            "visible": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "id",
+            "type",
+            "role",
+            "visible"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "id": {
+        "description": "Lowercase uuid (8-4-4-4-12 hex), e.g. 6f1e8a2c-4b0d-4c8e-9f3a-2d7b5e9c1a4f. Generate a fresh one per element and keep it stable across updates so a link keeps its click-tracking identity.",
+        "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
+        "type": "string"
+      },
+      "role": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": {
+        "const": "stack",
+        "type": "string"
+      },
+      "visible": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "id",
+      "type",
+      "role",
+      "visible",
+      "blockStyle",
+      "children"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / data / properties / end_time / anyOf

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

addedOutput schema / properties / data / properties / end_time / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / start_time / anyOf

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

addedOutput schema / properties / data / properties / start_time / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / data / properties / time_zone / anyOf

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

addedOutput schema / properties / data / properties / time_zone / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's added value is what it contributes beyond that: the resulting resource state (draft, not live), the 422 error on missing required fields, and server-side strict validation of the content tree. It does not cover permissions, rate limits, or whether create is safe to retry, so it is strong but not exhaustive.

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 sentences, front-loaded with the required-field contract and lifecycle note before the content-format detail. Dense and nearly waste-free, though the clause about content block-tree shape partially duplicates the schema's own long description.

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?

With an output schema present, annotations covering safety, and 91% schema coverage, the description needs only to add lifecycle and validation context, which it does (draft state, 422 behavior, strict server-side validation, get_content_schema pointer via the schema). Minor gaps remain around whether send_email or behaviour change the creation semantics, but nothing an agent needs to call it correctly 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 description coverage is 91% and the schema already explains content, smart_fields_conditions, signature_template_ids, and required fields in detail, so the baseline is 3. The description's only genuinely new parameter information is the cross-reference that content uses the same format as signature draft_content; the rest restates required fields and targeting parameters already documented.

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?

Opens with a specific verb+resource ("Create a marketing campaign") and immediately disambiguates from the sibling that activates campaigns by naming schedule_marketing_campaign. An agent can tell this apart from update_marketing_campaign, preview_marketing_campaign, and schedule_marketing_campaign without inspecting schemas.

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?

Explicitly states the lifecycle position: the campaign is created as a draft and schedule_marketing_campaign must be used to activate it, which is the key routing decision for this tool family. It does not mention preview_marketing_campaign or when to prefer update_marketing_campaign instead, so it stops short of full when/when-not coverage.

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

All Scribe Mail 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.