Circle MCP Server

Overview Schema Source Related Servers Discussions Admin

Create a community segment

create_community_segment

Destructive

Build a Circle community segment from contact filters or selected members; set confirm=true to apply this state-changing action.

Instructions

Create a community segment. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema

Name	Required	Description
`rules`	No
`title`	No
`account`	No	Named private Circle account; selects credentials, not a remote community ID.
`confirm`	No	Set true only when the user asked for exactly this action.
`payload`	No	Complete JSON request body instead of body flags. Supports nested Tiptap, maps and nullable values.
`visible`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`community_segment_consumer_attributes`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.1Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "rules": {
+    "properties": {
+      "rule_type": {
+        "enum": [
+          "all_contacts",
+          "all_members",
+          "custom_filters",
+          "selected_members"
+        ],
+        "type": "string"
+      },
+      "rules": {
+        "anyOf": [
+          {
+            "items": {
+              "properties": {
+                "filter_type": {
+                  "enum": [
+                    "is",
+                    "is_not",
+                    "contains",
+                    "does_not_contain",
+                    "gt",
+                    "lt",
+                    "eq"
+                  ],
+                  "type": "string"
+                },
+                "id": {
+                  "type": "string"
+                },
+                "key": {
+                  "type": "string"
+                },
+                "value": {
+                  "type": [
+                    "string",
+                    "boolean"
+                  ]
+                }
+              },
+              "required": [
+                "key",
+                "value"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          {
+            "items": {
+              "properties": {
+                "community_member_id": {
+                  "type": "integer"
+                },
+                "email": {
+                  "format": "email",
+                  "type": "string"
+                }
+              },
+              "required": [
+                "email",
+                "community_member_id"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          }
+        ]
+      }
+    },
+    "required": [
+      "rule_type",
+      "rules"
+    ],
+    "type": "object"
+  }
+}

changedInput schema / properties / confirm / description

Previous value: -"Must be true for the specific user-requested write."New value: +"Set true only when the user asked for exactly this action."

addedInput schema / properties / payload / properties / rules / $ref
```
Added value: +"#/$defs/rules"
```

removedInput schema / properties / payload / properties / rules / properties

Removed value: -{
-  "rule_type": {
-    "enum": [
-      "all_contacts",
-      "all_members",
-      "custom_filters",
-      "selected_members"
-    ],
-    "type": "string"
-  },
-  "rules": {
-    "anyOf": [
-      {
-        "items": {
-          "properties": {
-            "filter_type": {
-              "enum": [
-                "is",
-                "is_not",
-                "contains",
-                "does_not_contain",
-                "gt",
-                "lt",
-                "eq"
-              ],
-              "type": "string"
-            },
-            "id": {
-              "type": "string"
-            },
-            "key": {
-              "type": "string"
-            },
-            "value": {
-              "type": [
-                "string",
-                "boolean"
-              ]
-            }
-          },
-          "required": [
-            "key",
-            "value"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      {
-        "items": {
-          "properties": {
-            "community_member_id": {
-              "type": "integer"
-            },
-            "email": {
-              "format": "email",
-              "type": "string"
-            }
-          },
-          "required": [
-            "email",
-            "community_member_id"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    ]
-  }
-}

removedInput schema / properties / payload / properties / rules / required
```
Removed value: -[
-  "rule_type",
-  "rules"
-]
```
removedInput schema / properties / payload / properties / rules / type
```
Removed value: -"object"
```
addedInput schema / properties / rules / $ref
```
Added value: +"#/$defs/rules"
```

removedInput schema / properties / rules / properties

Removed value: -{
-  "rule_type": {
-    "enum": [
-      "all_contacts",
-      "all_members",
-      "custom_filters",
-      "selected_members"
-    ],
-    "type": "string"
-  },
-  "rules": {
-    "anyOf": [
-      {
-        "items": {
-          "properties": {
-            "filter_type": {
-              "enum": [
-                "is",
-                "is_not",
-                "contains",
-                "does_not_contain",
-                "gt",
-                "lt",
-                "eq"
-              ],
-              "type": "string"
-            },
-            "id": {
-              "type": "string"
-            },
-            "key": {
-              "type": "string"
-            },
-            "value": {
-              "type": [
-                "string",
-                "boolean"
-              ]
-            }
-          },
-          "required": [
-            "key",
-            "value"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      {
-        "items": {
-          "properties": {
-            "community_member_id": {
-              "type": "integer"
-            },
-            "email": {
-              "format": "email",
-              "type": "string"
-            }
-          },
-          "required": [
-            "email",
-            "community_member_id"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      }
-    ]
-  }
-}

removedInput schema / properties / rules / required
```
Removed value: -[
-  "rule_type",
-  "rules"
-]
```
removedInput schema / properties / rules / type
```
Removed value: -"object"
```

First observedv2.0.0Oct 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is largely covered. The description adds the mutation ('Changes community state') and the confirm=true gate, which is useful context, but does not explain what is destroyed, auth requirements, or side effects, and confirm is also documented in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and no filler. The terseness is efficient, though it borders on under-specification for a tool this complex.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with 8 parameters, nested objects, multiple request-body input modes (payload vs. flags vs. payload_file), and no output schema, the description omits nearly all operational detail. An agent would need to reverse-engineer the body-mode alternatives and rules structure from the schema alone.

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?

With 8 parameters (including nested rules and payload objects) at 50% schema coverage, the description needed to compensate but instead mentions no parameters. The only referenced behavior (confirm=true) is already fully described in the schema, so the description adds nothing to parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a precise verb and resource ('Create a community segment'), so an agent knows exactly what operation this performs. However, it is a near-verbatim restatement of the title and gives no differentiation from siblings like create vs. update_community_segment, duplicate_community_segment, or delete_community_segment.

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

Usage Guidelines2/5

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

The only usage-like hint is that confirm=true is required for the 'user-requested action', but there is no guidance on when to choose this tool over its close siblings (update/duplicate/delete_community_segment) and no stated preconditions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Create a community segment

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools