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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "broadcast_id": "<broadcast_id>"
    },
    "name": "broadcasts_unschedule"
  }
}

Input Schema

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

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

Changed1 schema field changedNov 2, 2026

changedOutput schema / $defs / Broadcast / properties / reply_to_email / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "An override for this email's Reply-To. Null uses the sender's current Reply-To when the email is sent.",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

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.3/5.0

Behavior4/5

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

Annotations already declare mutation, idempotency, and destructive behavior. The description adds useful context: workspace-change effect, retry after reading current state, and required permissions.

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?

Front-loads the core action and outcome, then adds only operational details: effect, retry guidance, permissions, and reference. No wasted sentences.

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 rich annotations, a complete input schema, and an output schema, the description supplies the remaining operational context an agent needs: state transition, permissions, and retry behavior.

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?

There is only one parameter and schema coverage is 100%, so the schema already defines broadcast_id. The description adds no additional parameter semantics beyond that baseline.

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: returning a scheduled Broadcast to draft state. The phrase "before delivery starts" distinguishes it from cancel/send siblings by timing and outcome.

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?

Gives a clear usage condition: use before delivery starts. It does not explicitly name broadcasts_cancel as the alternative once delivery has begun, so it stops short of full when/when-not guidance.

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

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources