Skip to main content
Glama

send_test_email

Send test emails to verify campaign content and formatting before distribution. Specify up to 5 recipient addresses to preview how your email appears across different inboxes.

Instructions

Send a test email for a campaign. test_emails: comma-separated addresses (max 5).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
test_emailsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The send_test_email function is an MCP tool handler that takes campaign_id and test_emails, formats them, and sends a POST request to the Mailchimp API /campaigns/{campaign_id}/actions/test endpoint.
    @mcp.tool()
    async def send_test_email(campaign_id: str, test_emails: str) -> str:
        """Send a test email for a campaign. test_emails: comma-separated addresses (max 5)."""
        mc = get_client()
        emails = [e.strip() for e in test_emails.split(",") if e.strip()]
        await mc.post(
            f"/campaigns/{campaign_id}/actions/test",
            json={"test_emails": emails[:5], "send_type": "html"},
        )
        return _fmt({
            "campaign_id": campaign_id,
            "sent_to": emails[:5],
            "message": "Test email sent.",
        })
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the action ('Send') and a constraint ('max 5' emails), but lacks details on permissions, rate limits, side effects (e.g., whether this triggers actual email delivery), or response format. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise—two brief sentences with zero wasted words. It front-loads the core purpose and efficiently adds parameter details, making it easy to parse quickly.

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 that an output schema exists, the description doesn't need to explain return values. However, as a mutation tool with no annotations and incomplete parameter documentation, it should provide more behavioral context (e.g., what 'send' entails, error conditions). The description is minimally adequate but has clear gaps.

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 0%, so the description must compensate. It explains 'test_emails' as 'comma-separated addresses (max 5)', adding useful semantics beyond the schema's generic 'string' type. However, it doesn't clarify 'campaign_id' (e.g., format or source), leaving half the parameters inadequately documented, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Send a test email') and the target resource ('for a campaign'), making the purpose understandable. However, it doesn't explicitly differentiate this tool from sibling tools like 'send_campaign' or 'replicate_campaign', which likely involve sending emails in different contexts.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing campaign), exclusions, or how it differs from similar tools like 'send_campaign', leaving the agent to infer usage from context alone.

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/AlexlaGuardia/mcp-mailchimp'

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