Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_segment

DestructiveIdempotent

Delete a segment or tag from an audience. Members remain in the audience. Requires audience ID and segment ID.

Instructions

Delete a segment or tag from an audience. Members remain in the audience.

Irreversible. Use update_segment to rename or modify conditions instead of deleting. Use list_segments to find segment IDs.

Returns 404 error if segment does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Segment/tag ID to delete (numeric string, e.g. '12345'). Obtain from list_segments.

Returns: JSON with status ("deleted"), segment_id.

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>",
      "segment_id": "<segment_id>"
    },
    "name": "delete_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
list_idYes
segment_idYes

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. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds that deletion is irreversible, members remain in the audience, and returns a 404 error if the segment does not exist. This goes beyond annotations by clarifying non-destructive impact on members and error cases.

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?

The description is well-structured: first sentence states purpose, then behavioral notes, alternative tool references, error case, followed by parameter documentation and return type. Every sentence is informative with no redundancy.

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?

Given the complexity of sibling delete tools and the presence of an output schema, the description covers purpose, behavior, error handling, parameter details, and return format. The only minor gap is the undocumented 'account' parameter, but it is optional and likely not needed for typical use.

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?

Input schema has 3 parameters (account, list_id, segment_id) with 0% schema description coverage. The description documents list_id and segment_id with examples and origin instructions, but completely omits the optional 'account' parameter. This adds value for the two required parameters but leaves 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?

The description starts with a clear verb-resource pairing: 'Delete a segment or tag from an audience.' It distinguishes from sibling tools like update_segment (rename/modify) and list_segments (find IDs), making the purpose unambiguous.

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 states when to use (delete) and when to use update_segment instead (to rename or modify conditions). Also advises using list_segments to find segment IDs, providing clear navigation among alternatives.

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