send16-mcp

Create draft campaign

create_campaign

Create a new email campaign as a draft: optionally with full HTML content and recipients (exactly ONE of audienceIds / segmentId / contactIds / tagIds / sendToAll) so it's ready to test and send. Nothing is sent until schedule_campaign.

Input Schema

Name	Required	Description
`html`	No	Full HTML body for the email (skip to design later)
`name`	Yes	Campaign name (internal label)
`apiKey`	No	Send16 API key (overrides SEND16_API_KEY env var)
`tagIds`	No	Target contacts with these tag IDs
`replyTo`	No	Reply-to email address
`subject`	Yes	Email subject line
`fromName`	Yes	Sender display name
`fromEmail`	Yes	Sender email (must be from a verified domain)
`segmentId`	No	Target this segment (see list_segments)
`sendToAll`	No	Target all subscribed contacts in the workspace
`contactIds`	No	Target these specific contact IDs
`audienceIds`	No	Target these audience IDs (see list_audiences)
`previewText`	No	Preview text shown in inbox alongside subject

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

changedInput schema / properties / fromEmail / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

changedInput schema / properties / replyTo / pattern

Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"

Changed10 schema fields changedAug 1, 2026

addedInput schema / properties / audienceIds

Added value: +{
+  "description": "Target these audience IDs (see list_audiences)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / contactIds

Added value: +{
+  "description": "Target these specific contact IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / fromName / maxLength
```
Previous value: -255New value: +100
```

addedInput schema / properties / html

Added value: +{
+  "description": "Full HTML body for the email (skip to design later)",
+  "type": "string"
+}

changedInput schema / properties / name / maxLength
```
Previous value: -255New value: +100
```
changedInput schema / properties / previewText / maxLength
```
Previous value: -255New value: +200
```

addedInput schema / properties / segmentId

Added value: +{
+  "description": "Target this segment (see list_segments)",
+  "type": "string"
+}

addedInput schema / properties / sendToAll

Added value: +{
+  "description": "Target all subscribed contacts in the workspace",
+  "type": "boolean"
+}

changedInput schema / properties / subject / maxLength
```
Previous value: -255New value: +200
```

addedInput schema / properties / tagIds

Added value: +{
+  "description": "Target contacts with these tag IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

First observedJul 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare it is a non-read-only, non-destructive, non-idempotent create; the description adds the important behavioral fact that creation is inert (draft) and sending is a separate step. It does not mention auth (the apiKey parameter) or any return value, but the draft/no-send guarantee is substantive context beyond the 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?

A single dense sentence that front-loads the action and state, then the targeting constraint, then the workflow boundary. No filler or repetition.

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?

For a 13-parameter create with full schema coverage and no output schema, the description covers the essential semantics: draft state, targeting exclusivity, and the send boundary. Minor gaps remain around the apiKey override and what the response returns, but nothing blocks correct invocation.

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 baseline is 3, but the description adds a real constraint not encoded in the schema: exactly ONE of audienceIds / segmentId / contactIds / tagIds / sendToAll must be supplied. That mutual-exclusivity rule is the key thing an agent could get wrong and is not derivable from the individual parameter descriptions.

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 (create), resource (email campaign), and resulting state (draft), which cleanly separates it from duplicate_campaign, update_campaign, and schedule_campaign. An agent can identify the tool's role without opening the schema.

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?

Explains the tool's place in the workflow: create as a draft so it is 'ready to test and send,' and explicitly notes 'Nothing is sent until schedule_campaign,' routing the agent to that sibling for sending. No explicit when-not guidance, but the lifecycle boundary is clear.

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

All send16-mcp 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 draft campaign

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources