Skip to main content
Glama
thenavidm

Circle MCP Server

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Reorder course lessons

reorder_course_lessons
Destructive

Rearrange course lessons and sections into a specified order within a Circle community. Confirm the change to update community state.

Instructions

Reorder course lessons. Changes community state and requires confirm=true for the user-requested action.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
space_idNoID of the course space
new_orderNo
payload_fileNoRegular local JSON body file, at most 5 MB. Cannot be mixed with body flags or payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv3.0.1
    • addedInput schema / $defs
      Added value: +{
+  "new_order": {
+    "description": "All course sections and lessons in their final order",
+    "items": {
+      "properties": {
+        "lesson_ids": {
+          "items": {
+            "type": "integer"
+          },
+          "type": "array"
+        },
+        "section_id": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "section_id",
+        "lesson_ids"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • 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 / new_order / $ref
      Added value: +"#/$defs/new_order"
    • removedInput schema / properties / new_order / description
      Removed value: -"All course sections and lessons in their final order"
    • removedInput schema / properties / new_order / items
      Removed value: -{
-  "properties": {
-    "lesson_ids": {
-      "items": {
-        "type": "integer"
-      },
-      "type": "array"
-    },
-    "section_id": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "section_id",
-    "lesson_ids"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / new_order / type
      Removed value: -"array"
    • addedInput schema / properties / payload / properties / new_order / $ref
      Added value: +"#/$defs/new_order"
    • removedInput schema / properties / payload / properties / new_order / description
      Removed value: -"All course sections and lessons in their final order"
    • removedInput schema / properties / payload / properties / new_order / items
      Removed value: -{
-  "properties": {
-    "lesson_ids": {
-      "items": {
-        "type": "integer"
-      },
-      "type": "array"
-    },
-    "section_id": {
-      "type": "integer"
-    }
-  },
-  "required": [
-    "section_id",
-    "lesson_ids"
-  ],
-  "type": "object"
-}
    • removedInput schema / properties / payload / properties / new_order / type
      Removed value: -"array"
  2. First observedv2.0.0

TDQS

B3.4/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 safety profile is covered. The description usefully adds that it 'changes community state' and needs confirm=true, but does not disclose what the reorder replaces (whole-order overwrite) or the confirm semantics beyond what the schema says.

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 zero padding, front-loading the operation and then the confirm requirement. It is appropriately sized, though the single terse line leaves room without being wasteful.

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

Completeness3/5

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

For a 6-parameter, nested-object mutation with no output schema, the description is thin: it never explains that new_order replaces the entire ordering, nor the payload/payload_file/body-flag alternatives. The confirm note is helpful, but key invocation details are left to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 83%, so the schema already documents space_id, account, confirm, payload and payload_file. The description adds no parameter-level meaning, and notably omits that new_order must be a complete ordered listing of all sections/lessons, which is the semantically critical detail.

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 description states a specific verb+resource ('Reorder course lessons'), which is clear and concrete. However it does not differentiate from siblings like update_course_lesson or update_course_section, which also mutate lesson/section ordering, so an agent must infer the distinction from the name alone.

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?

'requires confirm=true for the user-requested action' hints at the precondition for invoking it, but there is no explicit when-to-use versus when-not guidance and no mention of alternatives such as update_course_lesson for non-ordering edits. Usage is implied rather than stated.

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