Skip to main content
Glama
dazanza
by dazanza

send_test_email

Send test emails for Mailchimp campaigns to verify content and formatting before launching to your full audience.

Instructions

Send a test email for a campaign before sending to the full audience.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesCampaign ID
test_emailsYesArray of email addresses to send the test to
send_typeNoSend as HTML or plaintext (default: html)

Implementation Reference

  • The handler function for the send_test_email tool that calls the mailchimp SDK.
    async ({ campaign_id, test_emails, send_type }) => {
      await mailchimp.campaigns.sendTestEmail(campaign_id, {
        test_emails,
        send_type: send_type || "html",
      });
      return {
        content: [{ type: "text", text: JSON.stringify({ success: true, sent_to: test_emails }, null, 2) }],
      };
    }
  • server.js:247-264 (registration)
    Registration of the send_test_email tool using server.tool.
    server.tool(
      "send_test_email",
      "Send a test email for a campaign before sending to the full audience.",
      {
        campaign_id: z.string().describe("Campaign ID"),
        test_emails: z.array(z.string()).describe("Array of email addresses to send the test to"),
        send_type: z.enum(["html", "plaintext"]).optional().describe("Send as HTML or plaintext (default: html)"),
      },
      async ({ campaign_id, test_emails, send_type }) => {
        await mailchimp.campaigns.sendTestEmail(campaign_id, {
          test_emails,
          send_type: send_type || "html",
        });
        return {
          content: [{ type: "text", text: JSON.stringify({ success: true, sent_to: test_emails }, null, 2) }],
        };
      }
    );
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this requires specific permissions, if it's idempotent, what happens on failure, or any rate limits. The description only states the basic action without operational context.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded with the core functionality.

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

Completeness2/5

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

For a mutation tool (sending emails) with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error conditions, side effects, or how it interacts with campaign state. More context is needed given the tool's complexity.

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 parameters are well-documented in the schema. The description adds no additional parameter semantics beyond implying 'campaign_id' and 'test_emails' are needed for the test send, which is already clear from the schema. Baseline 3 is appropriate.

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 resource ('for a campaign'), specifying it's for testing before full audience sending. It distinguishes from siblings like 'send_campaign' by focusing on test functionality, though it doesn't explicitly name alternatives.

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 usage context ('before sending to the full audience'), suggesting this tool is for pre-launch validation. However, it doesn't explicitly state when to use this versus 'send_campaign' or other campaign-related tools, nor does it mention prerequisites or exclusions.

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

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