Mailrith Email Marketing

Get a sequence

sequences_get

Read-onlyIdempotent

Returns one sequence from the authenticated workspace. Permission: sequences:read. 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": {
      "sequence_id": "<sequence_id>"
    },
    "name": "sequences_get"
  }
}

Input Schema

Name	Required	Description	Default
`sequence_id`	Yes	The sequence 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 / Sequence / 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"
+  }
+]

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

addedOutput schema / $defs / BroadcastSendProgress / properties / sent
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / $defs / BroadcastSendProgress / required

Previous value: -[
-  "run_id",
-  "phase",
-  "selected",
-  "materialized",
-  "accepted",
-  "skipped",
-  "retrying",
-  "permanent_failed",
-  "unknown",
-  "canceled",
-  "percent_complete",
-  "effective_rate",
-  "provider_limited_rate",
-  "provider",
-  "estimated_completion",
-  "estimated_completion_basis",
-  "last_progress_at",
-  "pause_reason",
-  "next_retry_at",
-  "next_retry_action",
-  "pause_message",
-  "terminal"
-]New value: +[
+  "run_id",
+  "phase",
+  "selected",
+  "materialized",
+  "sent",
+  "accepted",
+  "skipped",
+  "retrying",
+  "permanent_failed",
+  "unknown",
+  "canceled",
+  "percent_complete",
+  "effective_rate",
+  "provider_limited_rate",
+  "provider",
+  "estimated_completion",
+  "estimated_completion_basis",
+  "last_progress_at",
+  "pause_reason",
+  "next_retry_at",
+  "next_retry_action",
+  "pause_message",
+  "terminal"
+]

addedOutput schema / $defs / SequenceEmail / properties / subject / description

Added value: +"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."

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

removedOutput schema / $defs / BroadcastSendProgress / properties / sent
```
Removed value: -{
-  "type": "integer"
-}
```

changedOutput schema / $defs / BroadcastSendProgress / required

Previous value: -[
-  "run_id",
-  "phase",
-  "selected",
-  "materialized",
-  "sent",
-  "accepted",
-  "skipped",
-  "retrying",
-  "permanent_failed",
-  "unknown",
-  "canceled",
-  "percent_complete",
-  "effective_rate",
-  "provider_limited_rate",
-  "provider",
-  "estimated_completion",
-  "estimated_completion_basis",
-  "last_progress_at",
-  "pause_reason",
-  "next_retry_at",
-  "next_retry_action",
-  "pause_message",
-  "terminal"
-]New value: +[
+  "run_id",
+  "phase",
+  "selected",
+  "materialized",
+  "accepted",
+  "skipped",
+  "retrying",
+  "permanent_failed",
+  "unknown",
+  "canceled",
+  "percent_complete",
+  "effective_rate",
+  "provider_limited_rate",
+  "provider",
+  "estimated_completion",
+  "estimated_completion_basis",
+  "last_progress_at",
+  "pause_reason",
+  "next_retry_at",
+  "next_retry_action",
+  "pause_message",
+  "terminal"
+]

removedOutput schema / $defs / SequenceEmail / properties / subject / description

Removed value: -"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."

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

addedOutput schema / $defs / SequenceEmail / properties / subject / description

Added value: +"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."

Changed2 schema fields changedAug 7, 2026

addedOutput schema / $defs / BroadcastSendProgress / properties / sent
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / $defs / BroadcastSendProgress / required

Previous value: -[
-  "run_id",
-  "phase",
-  "selected",
-  "materialized",
-  "accepted",
-  "skipped",
-  "retrying",
-  "permanent_failed",
-  "unknown",
-  "canceled",
-  "percent_complete",
-  "effective_rate",
-  "provider_limited_rate",
-  "provider",
-  "estimated_completion",
-  "estimated_completion_basis",
-  "last_progress_at",
-  "pause_reason",
-  "next_retry_at",
-  "next_retry_action",
-  "pause_message",
-  "terminal"
-]New value: +[
+  "run_id",
+  "phase",
+  "selected",
+  "materialized",
+  "sent",
+  "accepted",
+  "skipped",
+  "retrying",
+  "permanent_failed",
+  "unknown",
+  "canceled",
+  "percent_complete",
+  "effective_rate",
+  "provider_limited_rate",
+  "provider",
+  "estimated_completion",
+  "estimated_completion_basis",
+  "last_progress_at",
+  "pause_reason",
+  "next_retry_at",
+  "next_retry_action",
+  "pause_message",
+  "terminal"
+]

First observedJul 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context that annotations cannot carry: the required sequences:read permission and the authenticated-workspace boundary. It stops short of stating behavior on an unknown or unauthorized sequence_id.

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 short sentences with the core behavior front-loaded, followed by permission and reference. The API reference URL is boilerplate that adds little for an agent but costs almost nothing.

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, return values need no explanation, and annotations plus the stated permission cover the operational envelope. The only real gap is failure behavior for a missing or unauthorized sequence_id, which matters for a get-by-id tool.

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 a single parameter with 100% schema description coverage ("The sequence identifier."), so the schema already does the work. The description adds no format, origin, or lookup guidance for sequence_id, which is the baseline 3 case for a fully documented single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns one sequence from the authenticated workspace" gives a specific verb (returns) and a bounded resource (a single sequence), and the workspace scoping is meaningful. It implicitly distinguishes itself from sequences_list via "one", but never names the sibling, so the separation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the required sequence_id signals that this is a fetch-by-known-identifier operation, not a discovery call. There is no explicit statement of when to use this versus sequences_list or sequences_preview_journey, and no exclusions or prerequisites beyond the permission scope.

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.

Get a sequence

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources