Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create lesson

create_lesson
Destructive

Add a lesson at the end of a course, with text and a video link. Admins only. Adds a lesson page at the end of a course, as the course's Add page does: title, text and an optional video link that Skool plays above it. Uploaded videos and files are not supported. Published unless published is false; in a draft course nobody but admins sees it either way. Runs without asking first: nobody is notified.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group": "<group>",
      "course_id": "<course_id>",
      "title": "<title>"
    },
    "name": "create_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoLesson text. A blank line starts a new paragraph.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
titleYesLesson title.
course_idYescourse_id from list_courses or create_course.
publishedNofalse keeps it a draft. Default: true.
video_urlNoYouTube, Vimeo, Loom or Wistia link shown above the text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses auth requirements (admin only), default publication behavior, draft-course visibility, the absence of notifications, and that it runs without asking first. Those are exactly the behavioral traits an agent needs and that annotations do not convey.

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 first two sentences and the third sentence repeat the same information ('Add a lesson at the end of a course' / 'Adds a lesson page at the end of a course'). The content is front-loaded and useful, but that duplication wastes space.

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

Completeness4/5

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

For a six-parameter mutation tool with no output schema, the description covers auth, defaults, visibility, side effects, and media limitations well. It does not say what is returned or how failures (e.g., invalid course_id) are surfaced, which is a minor gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains where the video link appears ('Skool plays above it'), what published=true/false does in a draft course, and that the lesson is appended at the end. It adds more than the schema alone provides.

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 and resource ('Add a lesson at the end of a course') and scopes the content (text plus optional video link). It clearly separates this from update_lesson and create_course by implication but never names the siblings, so it falls short of the top score.

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

Usage Guidelines4/5

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

It gives a clear admin-only prerequisite, an explicit exclusion ('Uploaded videos and files are not supported'), and notes that it runs without confirmation. It does not explicitly route the agent to update_lesson for edits, which keeps it from a 5.

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

All Skool MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources