send16-mcp

create_campaign

Create a new email campaign in draft status, specifying subject, sender details, and optional preview text for review before sending.

Instructions

Create a new email campaign in Send16. The campaign is created in draft status and can be edited before sending.

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": {
      "name": "<name>",
      "subject": "<subject>",
      "fromName": "<fromName>",
      "fromEmail": "<fromEmail>"
    },
    "name": "create_campaign"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Campaign name (internal label)
`apiKey`	No	Send16 API key (overrides SEND16_API_KEY env var)
`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)
`previewText`	No	Preview text shown in inbox alongside subject

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.7Jul 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description discloses that the campaign is created in draft status, a key behavioral trait, but does not mention what the tool returns, error handling, or authentication requirements. With no annotations, more transparency would be beneficial.

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 sentence that is concise and front-loaded with the core purpose. No redundant or extraneous information.

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?

The description covers the essential purpose and draft status but lacks information about return values, error scenarios, and prerequisites. Given 7 parameters and no output schema, it is adequate but not complete.

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?

The description adds no parameter-specific information beyond the schema, which has 100% coverage. Per guidelines, baseline 3 applies when schema coverage is high and description adds no extra context.

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 the tool creates a new email campaign in Send16, specifying the verb 'create' and the resource 'email campaign'. It also mentions the draft status, which distinguishes it from sending or updating campaigns.

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?

The description implies usage when creating a campaign and notes it can be edited before sending, but it does not explicitly state when not to use this tool or provide alternatives. Sibling tools like update_campaign and send_campaign are not referenced.

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

Deploy Server