Skip to main content
Glama

unpublish_published_course

Destructive

Unpublish a course on your Skilljar domain to immediately stop learner access, while preserving enrollments, progress, and the ability to republish later.

Instructions

Take a course off a domain. Learners can no longer reach it.

    `id` is the published-course id - the publication, not the course.

    Sets `live` to false and FREES THE SLUG. The public URL stops working
    immediately, and the slug becomes available for another course to claim.

    The published course row survives, along with enrollments and learner progress.
    `republish_published_course` brings it back - but see that tool: the slug is
    REASSIGNED rather than restored, so the URL may differ.

    This is a soft, reversible action. `delete_published_course` does the same
    thing; this one is the clearer name for the intent.

    Requires the `published-courses:write` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
liveNo
slugNo
course_idNo
domain_idNo
is_hiddenNo
created_atNo
external_idNo
modified_atNo
open_accessNo
visible_on_catalogNo
access_period_ends_atNo
access_period_starts_atNo
visibility_override_typeNo
require_all_prerequisitesNo
allow_self_service_reenrollNo
unique_progress_per_enrollmentNo
restrict_access_start_end_datesNo
strict_enforce_group_visibilityNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that live is set to false, the slug is freed, the public URL stops working immediately, and the published course row, enrollments, and learner progress survive. It explicitly frames the action as soft and reversible, adding material behavioral context that annotations alone do not convey.

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 description is dense but well-structured, front-loaded with the core purpose, then covering the parameter, behavioral effects, reversibility, and auth. Most sentences earn their place; minor redundancy exists around slug freeing and the soft/reversible framing, but it does not hurt usability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is complete for this tool's complexity: one parameter fully explained, behavioral side effects covered, reversibility and sibling-tool relationship explained, and auth scope stated. An output schema exists, so return values need no additional explanation.

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

Parameters5/5

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

With only one parameter and 0% schema description coverage, the description carries the full burden and succeeds: it clearly defines `id` as the published-course id — the publication, not the course. This prevents a likely misuse of passing a course id instead.

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 opens with a specific verb and resource: 'Take a course off a domain. Learners can no longer reach it.' It also differentiates from siblings by explicitly naming delete_published_course and republish_published_course, leaving no ambiguity about what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit usage context: this is a soft, reversible action, delete_published_course does the same thing but this is the clearer name, and republish_published_course brings the course back with a caveat about slug reassignment. It also states the required OAuth scope.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server