Skip to main content
Glama

list_learner_progress

Read-onlyIdempotent

Track learner progress across all enrolled courses, including completed and required lesson counts, credits earned, and latest activity, to determine course completion percentages.

Instructions

How far a learner has got in every course they are enrolled in.

    `user_id` is the learner's Skilljar id. The SAME id works in v2 - `list_students`
    returns it - so no translation is needed between the two APIs.

    Answers what v2 cannot: `completed_lesson_count` against `lesson_count`,
    `completed_required_lesson_count` against `required_lesson_count`, credits
    earned, and `latest_activity`. v2's `list_enrollments` gives score and status but
    no lesson counts at all, so "40% of the way through" is only answerable here.

    COUNTS ONLY, NOT WHICH LESSONS. Skilljar's published v1 document describes a
    per-lesson endpoint; it returns 404 on the live API, so per-lesson detail is
    unavailable through any tool here. Do not report it as merely missing data.

    `enrollment_count` above 1 means the learner enrolled more than once. Read a low
    progress figure alongside it as a fresh attempt rather than lost work.

    Not paginated - every enrolment comes back at once.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
totalNo
user_idYes
progressYes
Install Server

TDQS

A5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses non-pagination, the separate v1 API credential requirement, the meaning of enrollment_count > 1, and the 404 behavior of the documented per-lesson endpoint. This is substantial behavioral context that an agent cannot infer from annotations alone.

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?

Though longer than many descriptions, every paragraph carries operationally necessary information: scope, id semantics, alternative tool comparison, limitations, edge-case interpretation, pagination, and credential. The content is front-loaded with the core purpose and each sentence earns its place.

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 one parameter, an output schema present, and annotations covering safety, the description fills every remaining gap: how to get the input, what distinguishes this endpoint, what is deliberately not returned, how to interpret an edge case, pagination behavior, and authentication. Nothing essential 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%, but the description fully defines user_id as the learner's Skilljar id, explains that the same id works in v2, and points to list_students as the way to obtain it. That is exactly the semantic clarification an agent needs for a single-parameter tool.

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 opening line states exactly what the tool computes: how far a learner has got in every enrolled course, which is a specific resource and measure. It further distinguishes itself from v2's list_enrollments by naming the unique lesson-count fields it exposes.

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 contrasts this tool with v2 alternatives, notes that '40% of the way through' is only answerable here, and warns that per-lesson detail is unavailable on the live API. It also tells the agent how to obtain user_id via list_students, so the call path is unambiguous.

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