Skip to main content
Glama

Create or update lesson content

upsert_lesson_content
DestructiveIdempotent

Creates or updates a rich course-owned article or embed. Articles must contain complete, learner-ready teaching content—not a placeholder or the lesson description alone. Updating the same authored activity is direct; replacing another activity requires the returned confirmation token and a new idempotency key.

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": {
      "course_id": "<course_id>",
      "lesson_id": "<lesson_id>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "content": "<content>"
    },
    "name": "upsert_lesson_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYesAccepts one of the documented argument shapes.
course_idYes
lesson_idYes
idempotency_keyYes
expected_revisionYes
replacement_confirmation_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description adds value beyond that: the replacement path needs a returned confirmation token plus a fresh idempotency key, and content must be learner-ready rather than an empty shell. It never contradicts the annotations, though it does not say what a replacement destroys or how it is reversible.

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?

Three sentences, front-loaded with the action and followed by the content-quality rule and the replacement condition. No filler, though the phrase 'updating the same authored activity is direct' is terse enough to need a second read.

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 six-parameter destructive mutation with a nested content object and no output schema, the description covers the content quality bar and the embed/token workflow well. Gaps remain: it never explains expected_revision or where the 'returned confirmation token' comes from, both of which an agent must resolve before calling correctly.

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?

Top-level schema description coverage is only 17%, but the nested content schema carries substantive descriptions for body_html, embeds and url. The description clarifies the semantics of idempotency_key and replacement_confirmation_token, yet says nothing about expected_revision, which is a required concurrency parameter for a destructive write.

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 opens with a specific verb and resource: 'Creates or updates a rich course-owned article or embed.' 'Course-owned' usefully distinguishes this from the library-content tools in the sibling list, and the article/embed split is spelled out. It stops short of naming which sibling handles the library equivalent, so the differentiation is implicit rather than explicit.

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 real selection rule: updating the same authored activity is direct, while replacing another activity requires a confirmation token and a new idempotency key. It also excludes a common misuse case ('not a placeholder or the lesson description alone'). It lacks explicit routing to alternatives such as update_library_content or attach_lesson_content.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources