send16-mcp

update_campaign

Update a draft campaign: name, subject, preview text, sender info, HTML content, and/or recipients. Retarget with exactly ONE of audienceIds / segmentId / contactIds / tagIds / sendToAll, then verify with preview_campaign_recipients before sending. Only drafts can be edited.

Input Schema

TableJSON Schema

Name	Required	Description
`html`	No
`name`	No	Campaign name (internal label)
`apiKey`	No	Send16 API key (overrides SEND16_API_KEY env var)
`tagIds`	No	Retarget to contacts with these tag IDs
`replyTo`	No
`subject`	No
`fromName`	No
`fromEmail`	No
`segmentId`	No	Retarget to this segment (see list_segments)
`sendToAll`	No	Retarget to all subscribed contacts in the workspace
`campaignId`	Yes	Campaign ID
`contactIds`	No	Retarget to these specific contact IDs
`audienceIds`	No	Retarget to these audience IDs (see list_audiences). Sets recipient type 'lists'.
`previewText`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedAug 1, 2026

addedInput schema / properties / audienceIds

Added value: +{
+  "description": "Retarget to these audience IDs (see list_audiences). Sets recipient type 'lists'.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / contactIds

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

addedInput schema / properties / name

Added value: +{
+  "description": "Campaign name (internal label)",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / segmentId

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

addedInput schema / properties / sendToAll

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

addedInput schema / properties / tagIds

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

removedInput schema / properties / templateSlug
```
Removed value: -{
-  "type": "string"
-}
```

First observedJul 12, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses key behavioral constraints: draft-only editing, the mutually exclusive retargeting requirement, and the recommended preview step. It does not mention error behavior or permissions, but the most critical operational traits are covered.

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 compact and efficiently structured: a clear verb-object first sentence, followed by a precise constraint on recipient selection, and a required verification step. Every sentence carries essential information with no 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 a 14-parameter mutation tool with no output schema and no annotations, the description covers the most critical context: partial updates allowed, draft-only restriction, recipient selection exclusivity, and a verification workflow. It omits response format and error semantics, but these are less critical given the schema and the practical workflow guidance.

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 57%, leaving several parameters undocumented. The description adds meaning by grouping content fields and, more importantly, by explaining the recipient-targeting parameters are mutually exclusive (exactly one of audienceIds/segmentId/contactIds/tagIds/sendToAll). This goes beyond raw schema definitions and clarifies how to choose among the retargeting options.

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 updates a draft campaign and enumerates the editable fields: name, subject, preview text, sender info, HTML content, and recipients. It distinguishes this from sibling tools like create_campaign or schedule_campaign by explicitly limiting updates to drafts.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage instructions: only drafts can be edited, retarget with exactly one of the listed recipient selectors, and verify with preview_campaign_recipients before sending. This provides concrete when-to-use and how-to-use guidance, clearly differentiating from related campaign tools.

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.

update_campaign

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources