Skip to main content
Glama
CloudSecurityAlliance

csa-skilljar

Official
by CloudSecurityAlliance
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

list_offers

Read-onlyIdempotent

Discover Skilljar items for sale and their prices. Browse offers for published courses, paths, or course series, including price in cents or training credits and availability dates.

Instructions

List what is for sale, and at what price.

    An offer binds a price to something purchasable - `published_course_id`,
    `published_path_id` or `course_series_id`, exactly one of which is set. Which one
    tells you what kind of thing is being sold.

    `price_cents` is in the offer's own `currency_code`; `price_credits` is the
    training-credit price, and an offer may have either or both. Neither is a
    discounted price - discounts live in promo-code pools.

    `starts_at` / `ends_at` bound availability, and `active` can be false
    independently of the dates.

    There are no filters on this endpoint; page through, or read `total`.

    Requires `CSA_SKILLJAR_V1_API_KEY`, a separate credential from the v2 client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
pageNo
rowsYes
totalNo
has_moreNo
next_pageNo
Install Server

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description adds significant behavioral context: no filtering, pagination behavior, availability fields, active being independent of dates, discount handling, and the distinct authentication credential required. This goes well beyond what annotations state.

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 front-loaded with the core purpose and each subsequent paragraph adds meaningful detail about pricing, availability, pagination, and credentials. It is somewhat long but every sentence serves a purpose and the blank-line structure improves readability.

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 simple unfiltered list endpoint with two optional pagination parameters and an output schema, the description is very complete: it explains offer semantics, price fields, discount exclusion, availability boundaries, pagination, and authentication requirements. Nothing essential is missing.

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

Parameters4/5

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

The input schema provides only names and types for 'page' and 'page_size' with 0% description coverage. The description compensates by stating there are no filters and instructing to 'page through, or read total', clarifying that these parameters control pagination rather than filtering.

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 'List what is for sale, and at what price,' giving a specific verb and resource. It further defines offer semantics by enumerating the purchasable object types, which clearly distinguishes the tool's scope even without naming siblings.

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

Usage Guidelines3/5

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

The description makes clear there are no filters and that callers should page through or read 'total', which implies when to use this endpoint. However, it does not explicitly name alternatives among the many list-related sibling tools or state when one should choose a different tool.

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