LearningSuite MCP Server

learningsuite_create_lesson

Create a lesson in a specific course section with video, HTML content, and thumbnail. Control lesson position and publish status.

Instructions

Create a lesson in a course section

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": {
      "courseId": "<courseId>",
      "sectionId": "<sectionId>",
      "name": "<name>"
    },
    "name": "learningsuite_create_lesson"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Lesson name
`courseId`	Yes	Course ID
`videoUrl`	No	Downloadable video URL
`sectionId`	Yes	Section ID
`htmlContent`	No	HTML content for the lesson
`thumbnailUrl`	No	Downloadable thumbnail image URL
`lessonSortPosition`	No	Position of the lesson in the section
`immediatelyPublishCourse`	No	Publish course immediately after creating lesson
`timestampInSecondsToGenerateThumbnail`	No	Video timestamp for thumbnail generation

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries full responsibility for disclosing behavioral traits. It only says 'create', implying mutation, but does not mention side effects like course publishing, required existing sections, or potential irreversible actions. The 'immediatelyPublishCourse' parameter hints at a side effect, but the description does not surface it.

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?

The description is a single concise sentence, front-loaded with the key action and context. It wastes no words and is appropriately sized for the purpose.

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?

Despite having 9 parameters and no output schema or annotations, the description is extremely minimal. It lacks information about return values, prerequisites (e.g., section must exist), or the meaning of key parameters beyond the schema. This is insufficient for a tool of this complexity.

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?

The input schema has 100% coverage with descriptions for all 9 parameters, so the baseline is 3. The tool description itself adds no parameter information beyond what the schema already provides, but does not need to compensate.

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?

The description clearly states a specific action (create) and resource (lesson) within a context (course section), using a verb+resource structure. It distinguishes this tool from siblings like create_group or create_member by focusing on 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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning context, prerequisites, or scenarios where other tools (e.g., get_module_lessons) would be more appropriate.

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

Deploy Server