Skip to main content
Glama

send16-mcp

by io.github.spruikco
OverviewDiscussionsAdmin

duplicate_campaign

Duplicate a campaign (template, content, and settings) as a new draft — works on sent campaigns too, so this is the way to re-use a past campaign's design. Optionally rename and retarget in the same call (exactly ONE of audienceIds / segmentId / contactIds / tagIds / sendToAll). NOTE: without retargeting, the copy keeps the ORIGINAL campaign's recipients.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the new draft (default: original name + ' (Copy)')
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
tagIdsNoRetarget the new draft to contacts with these tag IDs
segmentIdNoRetarget the new draft to this segment
sendToAllNoRetarget the new draft to all subscribed contacts
campaignIdYesCampaign ID to duplicate
contactIdsNoRetarget the new draft to these contact IDs
audienceIdsNoRetarget the new draft to these audience IDs (see list_audiences)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / audienceIds
      Added value: +{
+  "description": "Retarget the new draft to these audience IDs (see list_audiences)",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / campaignId / description
      Previous value: -"Campaign ID"New value: +"Campaign ID to duplicate"
    • addedInput schema / properties / contactIds
      Added value: +{
+  "description": "Retarget the new draft to these contact IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Name for the new draft (default: original name + ' (Copy)')",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / segmentId
      Added value: +{
+  "description": "Retarget the new draft to this segment",
+  "type": "string"
+}
    • addedInput schema / properties / sendToAll
      Added value: +{
+  "description": "Retarget the new draft to all subscribed contacts",
+  "type": "boolean"
+}
    • addedInput schema / properties / tagIds
      Added value: +{
+  "description": "Retarget the new draft to contacts with these tag IDs",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behaviors: what is copied, that it creates a new draft, works on sent campaigns, and the critical caveat that original recipients are kept without retargeting. It could mention response format or permission requirements, but the essential behavioral traits are well 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 three sentences with front-loaded purpose, followed by constraints and a caveat. Every sentence adds essential information without redundancy, making it concise and well-structured.

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

Completeness5/5

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

For an 8-parameter tool with no annotations and no output schema, the description is remarkably complete. It covers the action, use case, mutual exclusion of retargeting options, and default recipient behavior, giving an agent everything needed to invoke correctly.

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 schema already documents each parameter, so baseline is 3. The description adds meaningful semantic value by requiring exactly one of the five retargeting parameters and clarifying that omitting them preserves original recipients. This enriches the schema's bare parameter list.

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 duplicates a campaign (template, content, settings) as a new draft, which is a specific verb+resource action. It also distinguishes from siblings by noting it works on sent campaigns, making it the tool for re-using past design.

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?

The description provides a clear use case: re-use a past campaign's design, implying when to use this over creating a new campaign. It explicitly states the retargeting constraint (exactly ONE of ...) and explains the default behavior when no retargeting is given. However, it does not explicitly name alternative tools or say when not to use it.

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

All send16-mcp toolsInspect
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