Skip to main content
Glama
damientilman

Mailchimp MCP

by damientilman
OverviewSchemaRelated ServersScoreDiscussions
Python

list_connected_sites

Read-only

List all sites connected to your Mailchimp account to get their IDs and verify script installation status for tracking and pop-up forms.

Instructions

List all sites connected to this Mailchimp account for tracking and pop-up forms.

Use this to discover connected site IDs and check each site's script installation status. Use get_connected_site for the full record of a single site.

Authenticated via API key. Max 10 concurrent requests. Read-only, safe to retry.

Args: account: Optional account name (e.g. 'marketing') configured via MAILCHIMP_API_KEY_. Omit to use the default account. See list_accounts.

Returns: JSON with total_items and sites array. Each site: id, foreign_id, domain, site_script (object with url and fragment), status, created_at, updated_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A5/5.0
Behavior5/5

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

Adds value beyond annotations by specifying authentication via API key, max concurrent requests, and retry safety. Aligns with readOnlyHint and destructiveHint.

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 concise paragraphs with front-loaded purpose and no wasted words. Every sentence earns its place.

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?

Covers purpose, usage, parameter, output format with field details, auth, rate limits, and sibling tool reference. Complete for a simple list tool with good annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Explains the single optional parameter 'account' with example, reference to environment variable, and guidance to omit for default, fully compensating for 0% schema coverage.

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 it lists all connected sites for tracking and pop-up forms, and distinguishes from sibling 'get_connected_site' by specifying its use for full record of a single site.

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 tells when to use (discover site IDs, check script status) and when to use alternative (get_connected_site for single site), plus provides context on authentication and rate limits.

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