Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_member_note

DestructiveIdempotent

Delete a note permanently from a Mailchimp member. Use list_member_notes to find the note ID before calling.

Instructions

Permanently delete a note attached to a member. Cannot be undone.

Use list_member_notes to find note_ids before calling. Does not affect the member itself, only the note.

Returns 404 if the note or member does not exist.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member who owns the note. note_id: Note ID to delete. Obtain from list_member_notes.

Returns: JSON with status ('deleted'), email_address, note_id on success.

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": {
      "list_id": "<list_id>",
      "email_address": "<email_address>",
      "note_id": "<note_id>"
    },
    "name": "delete_member_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
list_idYes
note_idYes
email_addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. Addedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses 'Cannot be undone' and 'Permanently delete' beyond annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true). Notes that 404 is returned for nonexistent entities, which adds value. No contradiction with annotations.

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?

Front-loaded with purpose, then usage guidelines, then parameter documentation. Every sentence adds value with no repetition or fluff. Well-structured and concise.

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?

Covers key aspects: deletion action, permanence, prerequisites, error behavior, and success response format. Missing explanation of the optional 'account' parameter. Overall adequate for an agent to use correctly.

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 0%, so description must compensate. It explains list_id, email_address, and note_id with origins (list_audiences, member, list_member_notes). However, the optional 'account' parameter in schema is not mentioned, leaving a gap.

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 'Permanently delete a note attached to a member' with a specific verb and resource. Distinguished from siblings like delete_member and update_member_note by clarifying it only affects the note, not the member.

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?

Provides explicit guidance: 'Use list_member_notes to find note_ids before calling.' Mentions prerequisites and the 404 return if note or member doesn't exist. Does not compare directly to alternatives but gives clear context for correct usage.

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