Skip to main content
Glama

get_published_course

Read-onlyIdempotent

Fetch a published course's live status and access settings by its published-course ID to verify learner availability and manage domain publication.

Instructions

Fetch one course-to-domain publication and its access settings.

    `id` is the published-course id, NOT the course id. A course published to three
    domains has one course id and three published-course ids.

    `live` tells you whether learners can currently reach it. `slug` is the public
    URL path, and is null while the course is unpublished because unpublishing
    frees the slug for reuse.

    Requires the `published-courses:read` 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.8/5.0
Behavior5/5

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

Beyond the read-only annotations, the description adds valuable behavioral context: the id is specifically the published-course id rather than the course id, the slug is null while unpublished because it is freed for reuse, and the required OAuth scope is stated. This is substantive disclosure that helps an agent understand what the call does and what it needs.

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?

Every sentence earns its place: purpose, id clarification, key return-field semantics, and auth requirement. The information is front-loaded and tightly written 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?

With a single parameter and an output schema present, the description covers the essential context: id semantics, behavior of live and slug, and OAuth scope. Nothing needed for correct invocation is missing.

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%, so the description must carry the parameter documentation burden. It does so excellently by explaining that 'id' is the published-course id, not the course id, and illustrating the one-course-three-domains relationship. This provides meaning the bare schema cannot convey.

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: 'Fetch one course-to-domain publication and its access settings.' This clearly distinguishes the tool from list-oriented or mutation siblings, and the singular 'one' clarifies it is a single-record fetch.

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?

The description gives clear context for when to use the tool: when you need one published-course by its published-course id. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5, but the context is unambiguous enough for an agent to select it correctly.

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