Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Update a course lesson

update_course_lesson
Destructive

Update a Circle course lesson's name, status, body, media, or comment settings. Requires confirm=true because it changes community state.

Instructions

Update 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
lesson_idYesID of the course lesson
thumbnailNosigned_id of the lesson thumbnail image returned from the direct upload endpoint
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 destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation profile is covered. The description adds the confirm=true safety gate and notes it "changes community state," which is useful context, but it does not disclose what is destroyed, auth needs, or partial-update behavior.

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 mutation and confirm constraint front-loaded. Nothing is padded, though the brevity comes at the cost of missing detail rather than being truly economical.

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, nested-object mutation tool with no output schema and a 50% schema coverage, the description is far too thin. It omits the mutually exclusive input modes (payload_file vs. body flags vs. payload) that an agent must understand 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?

With 14 parameters and only 50% schema description coverage, the description carries a compensation burden it does not meet. It adds no meaning to lesson_id, account, payload vs. body flags vs. payload_file, or the nested rich_text_body, leaving several parameters ambiguous.

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 specific verb+resource ("Update a course lesson") that an agent can distinguish from the create/delete lesson siblings. However, it does not differentiate itself from closely related siblings like update_course_section, update_course_progress, or reorder_course_lessons.

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 guidance is a precondition ("requires confirm=true"), not a when-to-use rule. It names no alternatives, no when-not conditions, and no prerequisites such as the lesson needing to exist or which fields are mutable.

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