Mailrith Email Marketing

Unschedule a broadcast

broadcasts_unschedule

DestructiveIdempotent

Returns a scheduled Broadcast to draft state before delivery starts. Effect: workspace-change. Retry after reading the current resource state. Permissions: live_actions:write, broadcasts:write. API reference: https://mailrith.com/developers/api-reference.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`broadcast_id`	Yes	The broadcast identifier.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`response`	No
`request_id`	Yes	The stable correlation ID for this MCP tool invocation.
`operation_id`	Yes	The stable Mailrith public API operation ID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

changedOutput schema / $defs / BroadcastEmailDocument / description

Previous value: -"A structured email document. The root node must use type `doc` and contain supported block nodes."New value: +"A structured email document. The root node must use type `doc` and contain supported block nodes. For Subscriber personalization in email subjects and body text nodes, use Mailrith bracket tokens such as [Subscriber_Name, fallback=\"friend\"] or [Subscriber_Email, fallback=\"\"]. Before using a custom field, call custom_fields_list or custom_fields_get and copy its personalization_token exactly. Do not use Handlebars-style variables such as {{ subscriber.name }}; Mailrith sends them as literal text."

changedOutput schema / $defs / BroadcastEmailDocument / example / content

Previous value: -[
-  {
-    "content": [
-      {
-        "text": "Hello from Mailrith.",
-        "type": "text"
-      }
-    ],
-    "type": "paragraph"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
+        "type": "text"
+      }
+    ],
+    "type": "paragraph"
+  }
+]

changedOutput schema / $defs / BroadcastEmailDocument / examples

Previous value: -[
-  {
-    "content": [
-      {
-        "content": [
-          {
-            "text": "Hello from Mailrith.",
-            "type": "text"
-          }
-        ],
-        "type": "paragraph"
-      }
-    ],
-    "type": "doc"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "content": [
+          {
+            "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
+            "type": "text"
+          }
+        ],
+        "type": "paragraph"
+      }
+    ],
+    "type": "doc"
+  }
+]

Changed3 schema fields changedSep 3, 2026

changedOutput schema / $defs / BroadcastEmailDocument / description

Previous value: -"A structured email document. The root node must use type `doc` and contain supported block nodes. For Subscriber personalization in email subjects and body text nodes, use Mailrith bracket tokens such as [Subscriber_Name, fallback=\"friend\"] or [Subscriber_Email, fallback=\"\"]. Before using a custom field, call custom_fields_list or custom_fields_get and copy its personalization_token exactly. Do not use Handlebars-style variables such as {{ subscriber.name }}; Mailrith sends them as literal text."New value: +"A structured email document. The root node must use type `doc` and contain supported block nodes."

changedOutput schema / $defs / BroadcastEmailDocument / example / content

Previous value: -[
-  {
-    "content": [
-      {
-        "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
-        "type": "text"
-      }
-    ],
-    "type": "paragraph"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "text": "Hello from Mailrith.",
+        "type": "text"
+      }
+    ],
+    "type": "paragraph"
+  }
+]

changedOutput schema / $defs / BroadcastEmailDocument / examples

Previous value: -[
-  {
-    "content": [
-      {
-        "content": [
-          {
-            "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
-            "type": "text"
-          }
-        ],
-        "type": "paragraph"
-      }
-    ],
-    "type": "doc"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "content": [
+          {
+            "text": "Hello from Mailrith.",
+            "type": "text"
+          }
+        ],
+        "type": "paragraph"
+      }
+    ],
+    "type": "doc"
+  }
+]

Changed3 schema fields changedAug 17, 2026

changedOutput schema / $defs / BroadcastEmailDocument / description

Previous value: -"A structured email document. The root node must use type `doc` and contain supported block nodes."New value: +"A structured email document. The root node must use type `doc` and contain supported block nodes. For Subscriber personalization in email subjects and body text nodes, use Mailrith bracket tokens such as [Subscriber_Name, fallback=\"friend\"] or [Subscriber_Email, fallback=\"\"]. Before using a custom field, call custom_fields_list or custom_fields_get and copy its personalization_token exactly. Do not use Handlebars-style variables such as {{ subscriber.name }}; Mailrith sends them as literal text."

changedOutput schema / $defs / BroadcastEmailDocument / example / content

Previous value: -[
-  {
-    "content": [
-      {
-        "text": "Hello from Mailrith.",
-        "type": "text"
-      }
-    ],
-    "type": "paragraph"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
+        "type": "text"
+      }
+    ],
+    "type": "paragraph"
+  }
+]

changedOutput schema / $defs / BroadcastEmailDocument / examples

Previous value: -[
-  {
-    "content": [
-      {
-        "content": [
-          {
-            "text": "Hello from Mailrith.",
-            "type": "text"
-          }
-        ],
-        "type": "paragraph"
-      }
-    ],
-    "type": "doc"
-  }
-]New value: +[
+  {
+    "content": [
+      {
+        "content": [
+          {
+            "text": "Hello [Subscriber_Name, fallback=\"friend\"].",
+            "type": "text"
+          }
+        ],
+        "type": "paragraph"
+      }
+    ],
+    "type": "doc"
+  }
+]

First observedJul 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already include destructiveHint=true and idempotentHint=true. The description adds context beyond this by stating 'Effect: workspace-change' and specifying required permissions (live_actions:write, broadcasts:write). It also cautions to retry after reading current state, which is useful for concurrency. No contradiction with 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?

The description is compact, with the primary purpose in the first sentence. Additional facts (effect, retry, permissions, API link) are each presented in short, standalone segments. Every sentence adds value with no repetition or fluff.

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?

For a simple one-parameter tool with output schema and annotations, the description covers the action, preconditions, error handling, and permissions. The API reference provides further depth. It is fully sufficient for an agent to select and invoke the tool 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?

The schema only describes broadcast_id as 'The broadcast identifier.' The description implies the identifier must refer to a scheduled broadcast (not draft or sent), adding meaningful semantic context. Since schema coverage is 100%, this extra hint raises the score above the baseline of 3.

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 clearly states the specific action: 'Returns a scheduled Broadcast to draft state before delivery starts.' This distinguishes it from siblings like broadcasts_cancel, which likely cancels delivery entirely rather than reverting to draft.

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?

The phrase 'before delivery starts' provides a clear temporal condition for when to use the tool. 'Retry after reading the current resource state' offers operational guidance for handling failures, though it does not explicitly mention alternatives or when not to use it.

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

All Mailrith Email Marketing 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.

Unschedule a broadcast

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources