Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

update_segment

Idempotent

Update a Mailchimp segment's name or dynamic filter conditions. Specify only the fields to change; type conversion between static and dynamic is not supported.

Instructions

Update a segment's name or dynamic filter conditions.

Only provided fields are updated. Idempotent: re-applying the same name is safe. Cannot change a segment from static to dynamic or vice versa. Use add_members_to_segment or remove_members_from_segment to manage static segment membership instead.

Returns 404 error if segment_id is invalid. Providing match without conditions_json is ignored.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Segment ID to update (numeric string, e.g. '12345'). Obtain from list_segments. name: New display name for the segment. match: Condition match type for dynamic segments: 'all' (AND) or 'any' (OR). Must be provided together with conditions_json. conditions_json: JSON string of conditions array. Must be provided with match.

Returns: JSON with id, name, member_count, type ('static'/'saved'), options.

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": "update_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
matchNo
accountNo
list_idYes
segment_idYes
conditions_jsonNo

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.7/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and readOnlyHint=false. The description adds behavioral context: only provided fields are updated, idempotent reapplication, cannot change segment type, and error handling for invalid segment_id. No contradiction.

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?

Well-structured: core purpose first, then behavioral details, error info, and bulleted arg descriptions. Concise without redundancy. Front-loaded with the key action.

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 6 parameters (2 required) and the existence of an output schema, the description covers all relevant behaviors, constraints, error cases, and return values. It complements the schema and output schema well.

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?

Schema coverage is 0%, so description carries the burden. It explains list_id, segment_id, name, match, and conditions_json with examples and constraints. However, it does not describe the 'account' parameter present in schema, leaving a small 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 clearly states 'Update a segment's name or dynamic filter conditions,' specifying the resource (segment) and the actions. It distinguishes from siblings like create_segment, delete_segment, and membership management tools.

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 (update segment) and when not to (for static membership, use add_members_to_segment or remove_members_from_segment). Also explains constraints such as cannot change static/dynamic type and that match must be provided with conditions_json.

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