Skip to main content
Glama

publish_courses

Publish courses to domains for learner access using batch operations. Configure slugs, visibility, open access, and prerequisites to control course availability and enrollment.

Instructions

PUBLISH courses to domains, making them reachable by learners. BATCH.

    This is the tool that puts content in front of the public. Each item needs
    `course_id` and `domain_id`; everything else is optional.

    `slug` is the URL path and is CREATE-ONLY - it can be set here and never
    changed by `update_published_courses`. Omit it and Skilljar generates one from
    the title. Lowercase letters, numbers and dashes, two or more parts.

    MOST BOOLEANS DEFAULT FALSE, BUT TWO DEFAULT TRUE:
      `require_all_prerequisites`        defaults TRUE
      `unique_progress_per_enrollment`   defaults TRUE
    Everything else - `is_hidden`, `visible_on_catalog`, `open_access`,
    `restrict_access_start_end_dates`, `allow_self_service_reenroll`,
    `strict_enforce_group_visibility` - defaults false.

    `open_access` allows ANONYMOUS access: anyone with the URL, no sign-in.
    `visible_on_catalog` lists the course publicly. Both are off unless asked for.

    `visibility_override_type` is GROUP (the default) or CATEGORY.

    Publishing a course to a domain it is already on is a PER-ITEM conflict
    (`already_published`), not a whole-batch failure - the other items still land.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
published_coursesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
noteYes
totalYes
failedYes
succeededYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

Despite annotations being relatively sparse, the description discloses key behaviors: per-item conflict handling (`already_published` does not fail the batch), non-obvious boolean defaults (two default true), anonymous-access implications of `open_access`, and slug generation rules. This goes well beyond the structured metadata.

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 dense but each section earns its place: purpose, required vs optional fields, slug rules, boolean defaults, access semantics, conflict behavior, and auth scope. The formatting uses line breaks and capital flags to make the key defaults scannable.

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?

For a tool with a nearly empty item schema and no enums, this description is remarkably complete. It covers invocation requirements, field semantics, edge-case behavior for duplicate publishing, authorization, and points to an output schema for return details. Little is left for the agent to guess.

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?

The input schema only declares an array of objects with `additionalProperties: true`, so schema coverage is effectively 0%. The description fully compensates by documenting the required inner fields (`course_id`, `domain_id`), listing optional fields, explaining defaults, and defining slug format.

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: 'PUBLISH courses to domains, making them reachable by learners.' It also flags the batch nature, which immediately distinguishes it from list/get/update/unpublish operations on published courses.

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?

It explicitly frames this as 'the tool that puts content in front of the public,' states required per-item identifiers, and directly contrasts with `update_published_courses` by noting the slug is create-only and never changed by that sibling. The OAuth scope requirement further clarifies when the tool can be used.

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