Skip to main content
Glama
Aftab-web-dev

Email MCP Server

email_cold_campaign

Send personalized cold email campaigns using templates with placeholders for recipient name, company, and custom fields. Creates drafts by default for review before sending.

Instructions

Send personalized cold emails from a template. Supports placeholders: {{name}}, {{company}}, {{custom}}. Creates drafts by default for review before sending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNoCC recipients
bccNoBCC recipients
recipientsYesList of recipients with personalization data
body_templateYesHTML body with {{placeholders}}
create_draftsNoCreate as drafts first (recommended for review). Set false to send immediately.
delay_between_msNoDelay between sends in ms (avoids rate limits)
subject_templateYesSubject with {{placeholders}}
Behavior4/5

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

Explains default draft creation (with option to send immediately) and delay between sends to avoid rate limits. With no annotations, this provides useful behavioral context, though missing details on authentication or system rate limits.

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 efficient sentences convey purpose, placeholders, and default behavior without redundancy.

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?

Covers key aspects for a cold campaign tool: personalization, drafts, delay. Lacks description of return values or error handling, but still fairly complete given the schema covers parameters.

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 100%, but description adds value by reinforcing that placeholders ({{name}}, {{company}}, {{custom}}) are used in templates, linking the parameters to template usage.

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?

Clearly states the tool sends personalized cold emails from a template, using placeholders for personalization. Differentiates from sibling tools like email_send or email_draft by specifying cold campaign context.

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?

Implies usage for cold email campaigns with templates and personalization, but does not explicitly compare to alternative tools or state when not to use.

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/Aftab-web-dev/email-mcp-server'

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