Skip to main content
Glama
damientilman

Mailchimp MCP

get_account_info

Retrieve Mailchimp account details—name, contact info, total subscribers, and industry benchmarks—to verify API connectivity or inspect account-level metrics.

Instructions

Retrieve Mailchimp account details including name, contact info, total subscribers, and industry benchmarks.

Use this to verify API connectivity or inspect account-level metrics. Typically the first call in a workflow. Do not use this as a health check; use ping instead (faster, no payload). Use list_audiences to get per-audience stats.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Read-only, safe to retry.

Returns: JSON with fields: account_name (string), email (account owner), first_name, last_name, total_subscribers (int, all audiences combined), industry_stats (object with open/click rate benchmarks for the account's industry). Returns an error object if the API key is invalid or missing.

Example: get_account_info() -> {"account_name": "My Company", "total_subscribers": 5000, "industry_stats": {"open_rate": 0.21, ...}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, description fully discloses authentication (API key), rate limits (max 10 concurrent requests), safety (read-only, safe to retry), return structure (JSON with fields), and error handling (error object for invalid/missing key).

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?

Description is well-structured with clear sections (purpose, usage, behavioral notes, return info, example). Every sentence adds value without redundancy.

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

Completeness5/5

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

Given zero parameters and an output schema described in detail, the description completely covers purpose, authentication, rate limits, safety, return format, error handling, and provides an example. Everything an agent needs.

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?

Input schema is empty (0 parameters), and schema coverage is 100%, so baseline is 4. Description adds no parameter info since none exist, meeting the baseline.

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?

Description clearly states 'Retrieve Mailchimp account details' with specific fields (name, contact info, total subscribers, industry benchmarks). It distinguishes from siblings by noting it's typically first in a workflow and contrasts with ping and list_audiences.

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 provides when to use (verify API connectivity, inspect account-level metrics), when not to use (not as health check, use ping instead), and alternative (list_audiences for per-audience stats).

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

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