send16-mcp

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

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

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?

With no annotations, the description carries the burden and does well by disclosing two key behaviors: the campaign is created as a draft, and nothing is sent until schedule_campaign. It also highlights the 'exactly ONE of' exclusivity constraint among recipient parameters. Missing details like return value or permission requirements, but the safety-critical no-send behavior is clearly disclosed.

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 two sentences, front-loaded with the core purpose, and every word earns its place. It includes critical constraints and safety behavior without any redundancy or filler.

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?

Given the tool's high complexity (13 parameters, no output schema, no annotations), the description covers the key contextual points: draft creation, optional HTML/recipients, exclusivity constraint, and the fact that nothing is sent until schedule_campaign. It does not describe the return value, but the schema handles parameter details, and the description is sufficiently complete for selection and 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?

The input schema has 100% coverage with descriptions for all 13 parameters, so the baseline is 3. The description adds significant value by explaining the cross-parameter constraint: recipients must be exactly one of audienceIds/segmentId/contactIds/tagIds/sendToAll. This is not visible from the schema alone and helps correct invocation.

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?

The description clearly states 'Create a new email campaign as a draft' with a specific verb and resource, and distinguishes this from siblings like send_broadcast and schedule_campaign by explicitly noting that nothing is sent until schedule_campaign. This makes the tool's role unambiguous.

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?

It provides useful context that this tool is for creating a draft ready to test and send, and that sending happens later via schedule_campaign. However, it does not explicitly say 'use this instead of send_broadcast when you want to draft first' or name alternatives directly, so it falls just short of full 5.

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_campaign

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources