Courier

create_notification

Create a V2 notification template. name is required. Content may be provided inline or set separately afterwards. A newly created template is a draft; making it live is a separate step this tool cannot perform. Link a routing strategy via notification.routing.strategy_id to control which channels are used. Example: { notification: { name: 'welcome-email', tags: [], brand: null, subscription: null, routing: { strategy_id: 'rs_01abc' }, content: { version: '2022-01-01', elements: [] } } }.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No	Must be "DRAFT". These tools cannot publish.
`notification`	Yes	Notification template payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 15, 2026

changedInput schema / properties / notification / properties / brand / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / notification / properties / brand / description

Added value: +"Brand to apply, or null for none. Required on every call — never omit this key, and never send {}."

addedInput schema / properties / notification / properties / content / additionalProperties
```
Added value: +false
```

addedInput schema / properties / notification / properties / content / description

Added value: +"Elemental content, required on every call. Example: { version: \"2022-01-01\", elements: [{ type: \"text\", content: \"Hello!\" }] }."

addedInput schema / properties / notification / properties / content / properties

Added value: +{
+  "elements": {
+    "description": "Elemental content nodes",
+    "items": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "version": {
+    "description": "Content version identifier, e.g. \"2022-01-01\"",
+    "type": "string"
+  }
+}

addedInput schema / properties / notification / properties / content / required
```
Added value: +[
+  "version",
+  "elements"
+]
```
addedInput schema / properties / notification / properties / content / type
```
Added value: +"object"
```
addedInput schema / properties / notification / properties / name / description
```
Added value: +"Template display name"
```

changedInput schema / properties / notification / properties / routing / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "strategy_id": {
+        "description": "From a get_routing_strategy or list_notifications/get_notification response for THIS template's own intended strategy — never an id borrowed from an unrelated template found while searching for one.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "strategy_id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / notification / properties / routing / description

Added value: +"Routing strategy reference, or null to use the workspace default. Required on every call — never omit this key, and never send {}: the API rejects both an absent routing key and an empty object; if you have no strategy id, send null explicitly."

changedInput schema / properties / notification / properties / subscription / anyOf

Previous value: -[
-  {},
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "topic_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "topic_id"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / notification / properties / subscription / description

Added value: +"Subscription topic reference, or null for none. Required on every call — never omit this key, and never send {}."

addedInput schema / properties / notification / properties / tags / description
```
Added value: +"Tag list (use [] if none)"
```

changedInput schema / properties / notification / required

Previous value: -[
-  "name",
-  "tags"
-]New value: +[
+  "name",
+  "tags",
+  "brand",
+  "subscription",
+  "routing",
+  "content"
+]

changedInput schema / properties / state / description

Previous value: -"Template state after creation (defaults to DRAFT)"New value: +"Must be \"DRAFT\". These tools cannot publish."

changedInput schema / properties / state / enum

Previous value: -[
-  "DRAFT",
-  "PUBLISHED"
-]New value: +[
+  "DRAFT"
+]

AddedMay 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false), the description discloses that a newly created template defaults to draft, cannot be published through this tool, and may have content updated separately. This gives an agent important workflow context without contradicting any annotation.

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 front-loaded with the core purpose, then delivers constraints, workflow caveats, and a full example in a compact block. Every sentence conveys necessary decision-relevant information; the example is long but earned because it shows the required nested structure.

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 nested-object creation tool with no output schema, this is complete: the schema documents each field exhaustively, and the description adds the draft/publish lifecycle, routing intent, and the option to set content later. An agent has enough to construct a valid request and know what this tool does not do.

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?

Schema coverage is 100%, so the schema already documents parameters; the description adds value by explaining why routing is linked ('to control which channels are used') and showing a complete example of the required notification object. It reinforces that name is required and that content can be deferred, which is not evident from the JSON schema alone.

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 'Create a V2 notification template,' a specific verb and resource that immediately distinguishes creation from sibling get/archive/publish/replace notification tools. It also clarifies draft state and names required fields, so an agent can recognize what resource is being produced.

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 description explains this tool creates only drafts and explicitly states 'making it live is a separate step this tool cannot perform,' which tells the agent not to expect publication here. It also notes content may be supplied later, implying a follow-up content-editing tool, though it doesn't name sibling tools like publish_notification explicitly.

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

All Courier 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.

create_notification

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources