Skip to main content
Glama

archive_member

Remove a subscriber from a Mailchimp audience by archiving their profile, preserving data for future re-addition via add_or_update_member.

Instructions

Archive (soft-delete) a subscriber. They can be re-added later via add_or_update_member.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
emailYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the archive_member tool. It takes list_id and email, hashes the email via mc.subscriber_hash(), sends a DELETE request to Mailchimp's members endpoint, and returns a confirmation message.
    @mcp.tool()
    async def archive_member(list_id: str, email: str) -> str:
        """Archive (soft-delete) a subscriber. They can be re-added later via add_or_update_member."""
        mc = get_client()
        h = mc.subscriber_hash(email)
        await mc.delete(f"/lists/{list_id}/members/{h}")
        return _fmt({"email": email, "message": "Member archived."})
  • The tool is registered via the @mcp.tool() decorator on line 549, making it available as 'archive_member' in the MCP server.
    @mcp.tool()
    async def archive_member(list_id: str, email: str) -> str:
        """Archive (soft-delete) a subscriber. They can be re-added later via add_or_update_member."""
        mc = get_client()
        h = mc.subscriber_hash(email)
        await mc.delete(f"/lists/{list_id}/members/{h}")
        return _fmt({"email": email, "message": "Member archived."})
  • Input schema is implicitly defined by the function signature parameters (list_id: str, email: str) and the docstring 'Archive (soft-delete) a subscriber. They can be re-added later via add_or_update_member.'
    @mcp.tool()
    async def archive_member(list_id: str, email: str) -> str:
        """Archive (soft-delete) a subscriber. They can be re-added later via add_or_update_member."""
  • The subscriber_hash() static method used by archive_member to MD5-hash the email address for Mailchimp's API.
    @staticmethod
    def subscriber_hash(email: str) -> str:
        """MD5 hash of lowercase email — Mailchimp's subscriber identifier."""
        return hashlib.md5(email.lower().strip().encode()).hexdigest()
  • The delete() HTTP method on MailchimpClient, called by archive_member to DELETE the member.
    async def delete(self, path: str) -> Any:
        return await self._request("DELETE", path)
Behavior3/5

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

With no annotations, the description carries full burden. It indicates soft-deletion and reversibility, but does not disclose side effects (e.g., impact on tags, segments) or failure conditions.

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 sentences with no redundancy. Every word adds value.

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?

The description covers the core action and reversibility, but lacks details on success/error responses and prerequisites. Given the output schema exists, it partially compensates, but the description could be more complete for a mutation tool.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description does not explain the parameters beyond their names. For a tool with two required fields, adding context about expected values or constraints would be helpful.

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 the action ('Archive (soft-delete)') and the resource ('subscriber'). It distinguishes from permanent deletion by noting re-addability, which contrasts with the sibling 'delete_member_permanent'.

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

Usage Guidelines4/5

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

The description mentions that archived members can be re-added via 'add_or_update_member', providing an alternative. However, it does not explicitly state when to use this tool over other related tools like batch operations or permanent deletion.

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