Skip to main content
Glama

Unpublish course

unpublish_course
DestructiveIdempotent

Removes the live learner version and creates an editable draft copy. Run only after the user explicitly confirms that the course should stop being available to learners.

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>",
      "expected_revision": "<expected_revision>",
      "idempotency_key": "<idempotency_key>",
      "confirmation": "<confirmation>"
    },
    "name": "unpublish_course"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes
confirmationYes
idempotency_keyYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/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 covered structurally. The description adds genuinely new behavior: the live version is removed but a draft copy survives, and human confirmation is required first. It does not cover revision conflicts, idempotency replay behavior, or what happens to enrollments in progress.

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?

Two sentences, no filler, with the destructive effect stated first and the confirmation gate immediately after. Every clause earns its place.

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 destructive mutation with four mandatory, entirely undocumented parameters and no output schema, the description covers intent and the confirmation gate but leaves the mechanics of a correct call unexplained. An agent still needs the schema to discover the enum-literal confirmation string and the revision/idempotency requirements, which are exactly the parts most likely to be misused.

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

Parameters2/5

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

Schema description coverage is 0% across four required parameters, so the description must carry that burden and largely does not. It only vaguely gestures at `confirmation` via "user explicitly confirms" and never explains `expected_revision` (optimistic concurrency), `idempotency_key` (retry safety), or the literal "UNPUBLISH" value expected in `confirmation`.

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?

"Removes the live learner version and creates an editable draft copy" gives a specific verb plus the exact two-part effect, which separates it in spirit from delete_course and publish_course. It stops short of naming those siblings, so an agent must infer that unpublishing preserves a draft whereas deleting would not.

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?

Provides an explicit precondition: run only after the user explicitly confirms the course should stop being available to learners. That is real when-to-use guidance with a safety gate, but it does not name alternatives (delete_course for permanent removal, publish_course to restore availability) or say when unpublishing is the wrong choice.

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