Skip to main content
Glama
spruikco

send16-mcp

by spruikco

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCampaign name (internal label)
apiKeyNoSend16 API key (overrides SEND16_API_KEY env var)
replyToNoReply-to email address
subjectYesEmail subject line
fromNameYesSender display name
fromEmailYesSender email (must be from a verified domain)
previewTextNoPreview text shown in inbox alongside subject
Behavior3/5

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

No annotations provided, so description carries the burden. It discloses that campaigns start in draft status, but does not mention authentication, rate limits, or what happens on failure.

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?

Two sentences, no wasted words. Front-loaded with the core action, followed by a key detail about draft status.

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?

Given 7 parameters, no output schema, and no annotations, the description is adequate but lacks clarification on return values or post-creation steps beyond editing.

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?

Schema description coverage is 100%, so baseline is 3. The description does not add extra parameter semantics beyond what the schema already provides.

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 verb 'Create' and the resource 'email campaign'. It distinguishes from sibling tools like list_campaigns, delete_campaign, etc. by specifying the action and the platform (Send16).

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 when to use (to create a new campaign) and notes the draft status for editing, but does not provide explicit when-not-to-use or alternatives like update_campaign or duplicate_campaign.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/spruikco/send16-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server