HelpWell

Create a newsletter draft

create_newsletter

Saves a new newsletter draft from plain fields (subject, title, introduction, sections, button). Nothing is sent. This action uses the supplied content without AI generation or template selection.

Input Schema

Name	Required	Description
`html`	No	Optional: a full HTML body instead of the blocks (it is sanitized; the brand header, address and unsubscribe footer are added).
`name`	Yes	Internal name.
`title`	Yes	The headline.
`ctaUrl`	Yes	Button link (https).
`layout`	No
`eyebrow`	No	Small line above the title.
`signoff`	No	Closing line.
`subject`	Yes	Subject line.
`audience`	No	Who it goes to: contacts in ANY (match "any") or ALL (match "all") of the included segments, tags and filters, minus the excluded ones. Nothing included means every contact of the product. Consent and suppressions are always applied on top.
`ctaLabel`	Yes	Button label.
`fromName`	No	This email's own From name, like "AIMEE from Acme". Empty uses the sender name in Settings → Email.
`sections`	No	Body sections, each with a heading and body text.
`subjectB`	No	Optional second subject for an A/B test (half the audience gets each).
`preheader`	No	Preview text after the subject.
`productId`	No	Product id from list_products.
`introduction`	Yes	Opening paragraph(s). {{first_name}} and other merge tags work.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / fromName

Added value: +{
+  "description": "This email's own From name, like \"AIMEE from Acme\". Empty uses the sender name in Settings → Email.",
+  "maxLength": 100,
+  "type": "string"
+}

Changed10 schema fields changedOct 26, 2026

changedInput schema / properties / audience / properties / excludeFilters / description

Previous value: -"Conditions on contact fields. mode \"all\" or \"any\"; each rule is { field, operator, value }. Fields: contact.name, contact.email, contact.consent (subscribed | unknown | unsubscribed), contact.email_status, contact.product_id, contact.created_at, contact.last_seen_at, contact.attributes.<field> (tags are contact.attributes.tags), contact.events.<event>. Operators: is, is_not, contains, not_contains, gt, lt, exists, missing, before, after (dates are ISO or now-7d)."New value: +"Conditions on contact fields. mode \"all\" or \"any\"; each rule is { field, operator, value }. Fields: contact.name, contact.email, contact.consent (subscribed | unknown | unsubscribed), contact.email_status, contact.product_id, contact.created_at, contact.last_seen_at, contact.attributes.<field> (tags are contact.attributes.tags), contact.events.<event>. Operators: is, is_not, contains, not_contains, gt, gte, lt, lte, between (value and value2), any_of and none_of (value is a list of strings), exists, missing, before, after (dates are ISO or now-7d)."

changed

Input schema / properties / audience / properties / excludeFilters / properties / rules / items / properties / operator / enum

Previous value: -[
-  "is",
-  "is_not",
-  "contains",
-  "not_contains",
-  "gt",
-  "lt",
-  "exists",
-  "missing",
-  "before",
-  "after"
-]New value: +[
+  "is",
+  "is_not",
+  "contains",
+  "not_contains",
+  "gt",
+  "gte",
+  "lt",
+  "lte",
+  "between",
+  "any_of",
+  "none_of",
+  "exists",
+  "missing",
+  "before",
+  "after"
+]

added

Input schema / properties / audience / properties / excludeFilters / properties / rules / items / properties / value / anyOf

Added value: +[
+  {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / audience / properties / excludeFilters / properties / rules / items / properties / value / type
```
Removed value: -[
-  "string",
-  "number",
-  "boolean"
-]
```
addedInput schema / properties / audience / properties / excludeFilters / properties / rules / items / properties / value2
```
Added value: +{
+  "type": [
+    "string",
+    "number"
+  ]
+}
```

changedInput schema / properties / audience / properties / filters / description

Previous value: -"Conditions on contact fields. mode \"all\" or \"any\"; each rule is { field, operator, value }. Fields: contact.name, contact.email, contact.consent (subscribed | unknown | unsubscribed), contact.email_status, contact.product_id, contact.created_at, contact.last_seen_at, contact.attributes.<field> (tags are contact.attributes.tags), contact.events.<event>. Operators: is, is_not, contains, not_contains, gt, lt, exists, missing, before, after (dates are ISO or now-7d)."New value: +"Conditions on contact fields. mode \"all\" or \"any\"; each rule is { field, operator, value }. Fields: contact.name, contact.email, contact.consent (subscribed | unknown | unsubscribed), contact.email_status, contact.product_id, contact.created_at, contact.last_seen_at, contact.attributes.<field> (tags are contact.attributes.tags), contact.events.<event>. Operators: is, is_not, contains, not_contains, gt, gte, lt, lte, between (value and value2), any_of and none_of (value is a list of strings), exists, missing, before, after (dates are ISO or now-7d)."

changedInput schema / properties / audience / properties / filters / properties / rules / items / properties / operator / enum

Previous value: -[
-  "is",
-  "is_not",
-  "contains",
-  "not_contains",
-  "gt",
-  "lt",
-  "exists",
-  "missing",
-  "before",
-  "after"
-]New value: +[
+  "is",
+  "is_not",
+  "contains",
+  "not_contains",
+  "gt",
+  "gte",
+  "lt",
+  "lte",
+  "between",
+  "any_of",
+  "none_of",
+  "exists",
+  "missing",
+  "before",
+  "after"
+]

addedInput schema / properties / audience / properties / filters / properties / rules / items / properties / value / anyOf

Added value: +[
+  {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]

removedInput schema / properties / audience / properties / filters / properties / rules / items / properties / value / type
```
Removed value: -[
-  "string",
-  "number",
-  "boolean"
-]
```
addedInput schema / properties / audience / properties / filters / properties / rules / items / properties / value2
```
Added value: +{
+  "type": [
+    "string",
+    "number"
+  ]
+}
```

First observedOct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare the safety profile (readOnlyHint=false, destructiveHint=false), so the bar is lower; the description still adds real value by stating the persisted state is a draft and that nothing is dispatched, plus that no AI generation happens. It does not state that repeated calls create duplicate drafts (idempotentHint=false) or that a productId is needed to scope the draft.

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?

Two short sentences, front-loaded with the action and immediately followed by the key constraint. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter tool with a nested audience object and no output schema, the description is thin: it says nothing about segmentation/suppression semantics, the productId requirement, or what is returned (e.g., a draft id usable with preview_newsletter/update_newsletter). Adequate but with clear gaps.

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 94%, so the schema already documents nearly every field; the description only echoes a few required ones (subject, title, introduction, sections, button) and says nothing about the complex audience/filter object, productId, or the html alternative. Baseline 3 applies.

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?

Specific verb + resource ('Saves a new newsletter draft') with the content source spelled out ('plain fields'). It also explicitly carves itself out from the AI sibling: 'without AI generation or template selection', which separates it from generate_newsletter and use_email_template.

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?

'Nothing is sent' and 'uses the supplied content without AI generation' give a clear context for choosing this over the AI-generation and template paths, but no sibling is named and there is no explicit 'use X instead' routing.

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

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

Resources

Need Help?