Skip to main content
Glama
Sign In

Skool MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Update lesson

update_lesson
Destructive

Change a lesson's title, text or video link. Admins only. Edits one lesson page, as its Edit does: fields you leave out stay, body replaces the whole text. Members who completed it keep it completed. 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>",
      "lesson_id": "<lesson_id>"
    },
    "name": "update_lesson"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoNew text, replacing the old.
groupYesGroup URL name, e.g. 'yourgroup' for skool.com/yourgroup.
titleNoNew title.
lesson_idYeslesson_id from get_course or create_lesson.
video_urlNoNew video link; empty string removes the video.

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?

Goes well beyond the annotations: partial-update semantics ('fields you leave out stay'), the destructive outcome specific to body ('body replaces the whole text'), the side effect on member progress (completions are preserved), and the fact that it mutates without confirmation and sends no notifications. These are exactly the consequences an agent needs before firing a destructiveHint=true write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tight sentences, front-loaded with what changes and the admin gate, then escalating to consequences. No filler and nothing repeated from the schema verbatim.

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 destructive, non-idempotent mutation with no output schema, it covers permissions, partial-update behavior, member-progress impact, and notification silence. The only gap is the return value (whether the updated lesson is echoed back), which is minor here.

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 baseline is 3; the description adds genuine semantic information not in the schema by explaining that omitted fields are preserved and that body is a full replacement. It does not discuss video_url='' clearing the video (schema does) or group scoping, so it stays just above baseline.

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 ('Change') and resource ('a lesson') plus the exact editable fields (title, text, video link), and clarifies scope with 'Edits one lesson page'. It never names a sibling (create_lesson, get_lesson, mark_lesson_complete, update_post), so the boundary is inferable but not explicit.

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?

'Admins only' gives a real prerequisite, and the verb implies the use case is editing existing lesson content. But there is no when-not-to-use guidance and no reference to alternatives such as create_lesson for new pages or mark_lesson_complete for progress.

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