Skip to main content
Glama
Sign In
Skool MCP Server

Skool MCP Server

by cotletdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get lesson

get_lesson
Read-onlyIdempotent

Retrieves one accessible Skool Classroom lesson's text and linked video using group, course ID, and lesson ID, enabling agents to read lesson content and access its video.

Instructions

One lesson's text and video link.

Returns one Classroom lesson as its page shows it: the text (formatting dropped, paragraphs and list items kept) and the linked video. uploaded_video is true when the video was uploaded to Skool; get_video_transcript reads what is said in it. Attached files are not returned. Only lessons this account can open.

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>",
      "lesson_id": "<lesson_id>"
    },
    "name": "get_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
course_idYescourse_id from list_courses or create_course.
lesson_idYeslesson_id from get_course or list_courses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive), it discloses the lossy transformation applied to output (formatting dropped, paragraphs and list items kept), an explicit exclusion ('Attached files are not returned'), and an access constraint ('only lessons this account can open'). These are exactly the traits an agent cannot infer from the schema or hints.

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?

The return contents are front-loaded in the first line, with behavioral caveats following in a compact block. Three sentences carry real information, though 'Returns one Classroom lesson as its page shows it' partly restates the opening line and could be merged.

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?

With no output schema, the description correctly takes on the burden of describing the return shape (text, video link, uploaded_video flag) and what is omitted (attachments, formatting). It does not address edge cases such as a lesson with no video or empty text, which would complete the picture for an openWorld read.

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 100% and each of the three required parameters is documented in the schema with provenance ('from list_courses or create_course', 'from get_course or list_courses'). The description adds no per-parameter detail beyond the implicit link between 'lessons this account can open' and the group scope, so the baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource ('One lesson's text and video link' / 'Returns one Classroom lesson as its page shows it') and enumerates exactly what comes back: text with formatting dropped, plus the linked video. It is clearly separable from get_course (course container) and get_video_transcript (spoken content), both of which appear in the sibling list.

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?

Routes the agent explicitly: uploaded_video indicates an uploaded video, and 'get_video_transcript reads what is said in it' names the alternative for transcript needs. It also gives a precondition ('Only lessons this account can open'), but does not state when to prefer get_course or list_courses over this, so it stops short of full when/when-not 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