Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Create a course lesson

create_course_lesson
Destructive

Add a lesson to a Circle course section, setting status, body, media, and comments. Requires confirm=true because it changes community state.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
statusNo
accountNoNamed private Circle account; selects credentials, not a remote community ID.
confirmNoSet true only when the user asked for exactly this action.
payloadNoComplete JSON request body instead of body flags. Supports nested Tiptap, maps and nullable values.
body_htmlNo
thumbnailNosigned_id of the lesson thumbnail image returned from the direct upload endpoint
section_idNo
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.
featured_mediaNosigned_id of the lesson featured media file returned from the direct upload endpoint
rich_text_bodyNo
is_comments_enabledNo
is_featured_media_enabledNo
is_featured_media_download_enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "rich_text_body": {
+    "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 / rich_text_body / $ref
      Added value: +"#/$defs/rich_text_body"
    • removedInput schema / properties / payload / properties / rich_text_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 / rich_text_body / type
      Removed value: -"object"
    • addedInput schema / properties / rich_text_body / $ref
      Added value: +"#/$defs/rich_text_body"
    • removedInput schema / properties / rich_text_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 / rich_text_body / type
      Removed value: -"object"
  2. First observedv2.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. "Changes community state" largely restates that, but the confirm=true requirement is genuine behavioral context not present in the annotations, which earns some credit.

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 tight sentences with the core action front-loaded and no filler. Efficient, though the second sentence mixes state-change and confirm semantics compactly rather than organizing them.

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 14-parameter, 0-required, nested-object mutation tool with no output schema, the description is far too thin. It omits the payload vs body-flags vs payload_file exclusivity, section_id requirement, and draft/published status semantics that an agent needs to invoke it correctly.

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 43% across 14 parameters (payload nesting, rich_text_body, section_id, thumbnail, featured_media, body flags all undocumented), so the description is expected to compensate. Instead it mentions only confirm, leaving the bulk of parameters unexplained beyond the schema.

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?

States a clear verb+resource ("Create a course lesson") that an agent can distinguish from update_course_lesson and delete_course_lesson by verb alone. However, it offers no sibling differentiation beyond the obvious verb, so it does not reach a 5.

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 description never says when to use this versus update_course_lesson, create_course_section, or other creation siblings, nor any prerequisites. The only usage-adjacent note (confirm=true for the user-requested action) is a parameter rule rather than tool-selection guidance.

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