Skip to main content
Glama

update_published_courses

Batch-update published courses to change their behavior, such as access periods, open access, and catalog visibility. Rejects immutable fields like slug, course_id, and domain_id.

Instructions

Change how an already-published course behaves. This is a BATCH operation.

    `published_courses` is the batch: every item needs an `id`, the
    published-course id, plus the fields to change.

    THREE FIELDS CANNOT CHANGE AFTER PUBLISHING: `slug`, `course_id` and
    `domain_id`. Skilljar accepts them here and silently ignores them, so this tool
    rejects them instead of letting you believe the change happened. To move a
    course to a different slug or domain, unpublish and publish again - and expect
    the old URL to stop working.

    Sending `access_period_starts_at` or `access_period_ends_at` as null CLEARS the
    date. Omitting the key leaves it alone.

    Changing `open_access` or `visible_on_catalog` changes what anonymous visitors
    can see, immediately.

    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?

Beyond the sparse annotations (readOnly=false, idempotent=false, destructive=false), the description discloses important behaviors: it rejects silently-ignored fields, null clears dates while omission leaves them unchanged, and open_access/visible_on_catalog changes take immediate public effect. It also states the required OAuth scope. No contradiction with annotations.

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 front-loaded with the core purpose, then organized into focused paragraphs for batch structure, immutable fields, null semantics, immediate visibility, and auth. Every sentence carries meaningful operational information with no filler.

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 an opaque schema and significant edge-case behavior, this description is remarkably complete. It covers payload structure, rejected fields, null behavior, visibility changes, and authorization scope. The output schema exists, so return-value documentation is not the description's burden.

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?

Schema coverage is 0%, and the single parameter is just an array of additionalProperties objects. The description fully compensates by explaining that each item needs an id, the published-course id, plus fields to change, and it names several semantically important fields and their null/omission behavior. Without this, an agent would have no idea how to construct the batch payload.

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: 'Change how an already-published course behaves.' It immediately clarifies this is a batch operation, distinguishing it from single-item tools and from publish/unpublish/republish siblings. The phrasing clearly separates it from update_courses by specifying 'already-published.'

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 explicitly states when this tool is appropriate and when it is not. It names the immutable fields (slug, course_id, domain_id) and gives the alternative workflow: 'unpublish and publish again.' It also explains the null vs. omitted distinction, which is critical for correct usage. This is actionable routing guidance.

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