Circle MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Image Post

create_image_post

Destructive

Publishes an image post to a Circle community space, supporting draft, scheduled, or published status. Requires confirm=true to apply the user-requested change.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No
`status`	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.
`user_id`	No	id of the author
`space_id`	Yes	Image space ID
`is_pinned`	No	whether the post should be pinned to the top
`user_email`	No	email of the author (preferred over user_id)
`tiptap_body`	No
`payload_file`	No	Regular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
`is_liking_enabled`	No
`gallery_attributes`	No
`is_comments_enabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv3.0.1Oct 7, 2026

addedInput schema / $defs

Added value: +{
+  "gallery_attributes": {
+    "properties": {
+      "downloadable_images": {
+        "type": "boolean"
+      },
+      "images_attributes": {
+        "items": {
+          "properties": {
+            "height": {
+              "type": "integer"
+            },
+            "id": {
+              "type": "integer"
+            },
+            "image": {
+              "type": "string"
+            },
+            "width": {
+              "type": "integer"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "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 / gallery_attributes / $ref
```
Added value: +"#/$defs/gallery_attributes"
```

removedInput schema / properties / gallery_attributes / properties

Removed value: -{
-  "downloadable_images": {
-    "type": "boolean"
-  },
-  "images_attributes": {
-    "items": {
-      "properties": {
-        "height": {
-          "type": "integer"
-        },
-        "id": {
-          "type": "integer"
-        },
-        "image": {
-          "type": "string"
-        },
-        "width": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

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

removedInput schema / properties / payload / properties / gallery_attributes / properties

Removed value: -{
-  "downloadable_images": {
-    "type": "boolean"
-  },
-  "images_attributes": {
-    "items": {
-      "properties": {
-        "height": {
-          "type": "integer"
-        },
-        "id": {
-          "type": "integer"
-        },
-        "image": {
-          "type": "string"
-        },
-        "width": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedInput schema / properties / payload / properties / gallery_attributes / type
```
Removed value: -"object"
```

First observedv2.0.0Oct 2, 2026

TDQS

C2.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation profile is covered structurally. The description adds the confirm=true gating requirement and that community state changes, which is genuine extra context, but it stops short of saying what is created/destroyed or what permissions are needed.

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

Conciseness3/5

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

The description is short and front-loads the behavioral note, but the first sentence is a wasted restatement of the title. It is not padded, yet one of its two sentences does not earn its place.

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 15-parameter destructive mutation tool with nested objects, 53% schema coverage, and no output schema, the description is far too thin. It omits the confirm semantics details, parameter interactions, and any indication of success/failure behavior that an agent would need.

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?

The description explains none of the 15 parameters, including the required space_id, the status enum, the account selector, or the mutually exclusive payload/payload_file/body-flag options. With schema description coverage at only 53% and heavy nesting, the description should compensate but adds nothing about parameter meaning.

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

Purpose2/5

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

The description's first sentence, 'Create Image Post', is a verbatim restatement of the title, making it tautological. It names no scope, no distinguishing feature versus siblings like create_post, create_embed, or duplicate_image_post, so an agent gains nothing beyond what the title already says.

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?

There is no when-to-use or when-not-to-use guidance. With many sibling creation tools (create_post, create_event, create_embed, duplicate_image_post), the description never explains what selects this tool over them. The confirm=true remark concerns invocation hygiene, not tool selection.

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

Deploy Server

Create Image Post

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools