Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

create_verified_domain

Sends a verification code to the provided email address to begin verifying a domain for Mailchimp usage.

Instructions

Begin domain verification by sending a verification code to an address at that domain.

The domain is derived from the part of verification_email after the '@'. Mailchimp emails a code to this address; pass it to verify_verified_domain to complete verification. Use list_verified_domains to check existing domains before starting.

Args: verification_email: A mailbox at the domain to verify (e.g. 'admin@mail.example.com'). The verification code is sent here.

Returns: JSON with domain, verified (boolean), authenticated (boolean), verification_status, authentication_status.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "verification_email": "<verification_email>"
    },
    "name": "create_verified_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
verification_emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that it sends a verification code to the email, domain derivation, and further steps. Annotations are minimal, so description carries the burden well. Could mention idempotency or error conditions, but overall good transparency.

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?

Concise and well-structured: first sentence states purpose, followed by step details, then parameter and return sections. No unnecessary words.

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?

Explains the verification flow and references sibling tools. Missing details about the account parameter and potential error cases, but otherwise complete for a multi-step process.

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?

Adds meaning for the required verification_email with an example and its role. However, the optional account parameter is not described at all. With 0% schema coverage, description partially compensates but misses one parameter.

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 it begins domain verification by sending a verification code. It distinguishes from siblings like list_verified_domains and verify_verified_domain, making the tool's role in the workflow explicit.

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

Usage Guidelines5/5

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

Explicitly advises checking existing domains with list_verified_domains before starting, and to use verify_verified_domain after receiving the code. Provides clear when-to-use and when-not-to-use guidance.

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

Deploy Server

Other Tools