Circle MCP Server

Overview Schema Source Related Servers Discussions Admin

Update Basic Post

update_post

Destructive

Update an existing Circle community post's content, metadata, topics, or settings. Set confirm=true to approve this state-changing action.

Instructions

Update Basic Post. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`topics`	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.
`post_id`	Yes
`is_pinned`	No
`meta_title`	No
`cover_image`	No	signed_id of the cover image
`tiptap_body`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`published_at`	No
`hide_meta_info`	No
`opengraph_title`	No
`meta_description`	No
`is_liking_enabled`	No
`is_comments_closed`	No
`skip_notifications`	No
`is_comments_enabled`	No
`internal_custom_html`	No
`opengraph_description`	No
`is_truncation_disabled`	No
`hide_from_featured_areas`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv3.0.1Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "tiptap_body": {
+    "description": "The Tiptap body will be updated only for posts that already contain a Tiptap body. If the post does not have a Tiptap body, the tiptap_body will be ignored.",
+    "properties": {
+      "body": {
+        "properties": {
+          "content": {
+            "items": {
+              "properties": {
+                "attrs": {
+                  "type": "object"
+                },
+                "marks": {
+                  "items": {
+                    "type": "object"
+                  },
+                  "type": "array"
+                },
+                "text": {
+                  "type": [
+                    "string",
+                    "null"
+                  ]
+                },
+                "type": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "type",
+          "content"
+        ],
+        "type": "object"
+      }
+    },
+    "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 / tiptap_body / $ref
```
Added value: +"#/$defs/tiptap_body"
```

removedInput schema / properties / payload / properties / tiptap_body / description

Removed value: -"The Tiptap body will be updated only for posts that already contain a Tiptap body. If the post does not have a Tiptap body, the tiptap_body will be ignored."

removedInput schema / properties / payload / properties / tiptap_body / properties

Removed value: -{
-  "body": {
-    "properties": {
-      "content": {
-        "items": {
-          "properties": {
-            "attrs": {
-              "type": "object"
-            },
-            "marks": {
-              "items": {
-                "type": "object"
-              },
-              "type": "array"
-            },
-            "text": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "type": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "type": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "content"
-    ],
-    "type": "object"
-  }
-}

removedInput schema / properties / payload / properties / tiptap_body / type
```
Removed value: -"object"
```
addedInput schema / properties / tiptap_body / $ref
```
Added value: +"#/$defs/tiptap_body"
```

removedInput schema / properties / tiptap_body / description

Removed value: -"The Tiptap body will be updated only for posts that already contain a Tiptap body. If the post does not have a Tiptap body, the tiptap_body will be ignored."

removedInput schema / properties / tiptap_body / properties

Removed value: -{
-  "body": {
-    "properties": {
-      "content": {
-        "items": {
-          "properties": {
-            "attrs": {
-              "type": "object"
-            },
-            "marks": {
-              "items": {
-                "type": "object"
-              },
-              "type": "array"
-            },
-            "text": {
-              "type": [
-                "string",
-                "null"
-              ]
-            },
-            "type": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "type": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "content"
-    ],
-    "type": "object"
-  }
-}

removedInput schema / properties / tiptap_body / 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 mark this as a destructive, non-idempotent, open-world write operation. The description adds that it changes community state and requires confirm=true, which is useful mutation context, but it does not detail permissions, reversibility, or side effects.

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?

It is two sentences, front-loaded, and free of filler. The first sentence restates the title, while the second adds mutation and confirm requirements, so it is efficient though sparse.

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 23-parameter destructive update with no output schema and very low schema coverage, the description barely scratches the surface. It gives the confirm requirement but omits payload-vs-body-flag behavior, tiptap_body handling, and field-specific update semantics.

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?

Schema description coverage is 22%, so the description needs to compensate, but it only mentions confirm=true and says nothing about post_id, payload, payload_file, tiptap_body, or the other 18 parameters. The confirm note largely duplicates existing schema guidance, leaving most parameters undocumented.

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

Purpose3/5

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

The description identifies a verb and resource ('Update Basic Post'), but 'Basic Post' is not defined and the description does not distinguish this tool from create_post, delete_post, get_post, or explain what fields are updateable. It is minimally clear but vague.

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

Usage Guidelines3/5

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

The only usage signal is the confirm=true prerequisite tied to user-requested actions. It does not name alternatives or explain when to use this versus get_post, create_post, or delete_post.

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

Deploy Server

Update Basic Post

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools