Skip to main content
Glama

List Course Recordings

list-course-recordings
Read-onlyIdempotent

List public class recordings (lecture audio with a transcript) that students shared for a course. Pass course_id from search-courses. Most recently recorded first; each recording has a recording date and an artifact_id. An empty list means no one has shared a recording for this course yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>"
    },
    "name": "list-course-recordings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many recordings to return. Integer from 1 to 20. Default 10.
course_idYesNumeric course id from search-courses. Example: 1581710. A numeric string such as "1581710" is accepted.

Output Schema

NameRequiredDescriptionDefault
course_idYesCourse id whose recordings were listed.
recordingsYesPublic class recordings for this course, most recently recorded first. Empty when none are shared yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / recordings / description
      Previous value: -"Public class recordings for this course, newest upload first. Empty when none are shared yet."New value: +"Public class recordings for this course, most recently recorded first. Empty when none are shared yet."
    • removedOutput schema / properties / recordings / items / properties / created_at
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "description": "When the recording was uploaded, ISO 8601 in UTC. Null when the date is unknown."
      -}
    • addedOutput schema / properties / recordings / items / properties / recorded_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "When the lecture was recorded, ISO 8601 in UTC: the date stored in the audio file when it has one, otherwise the upload time. Null when unknown."
      +}
    • changedOutput schema / properties / recordings / items / required
      Previous value: -[
      -  "artifact_id",
      -  "title",
      -  "duration_seconds",
      -  "created_at",
      -  "project_id"
      -]New value: +[
      +  "artifact_id",
      +  "title",
      +  "duration_seconds",
      +  "recorded_at",
      +  "project_id"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / course_id / maximum
      Previous value: -9007199254740991New value: +2147483647
  3. Changed3 schema fields changed
    • changedOutput schema / properties / recordings / description
      Previous value: -"Public class recordings for this course, most recently updated first. Empty when none are shared yet."New value: +"Public class recordings for this course, newest upload first. Empty when none are shared yet."
    • addedOutput schema / properties / recordings / items / properties / created_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "When the recording was uploaded, ISO 8601 in UTC. Null when the date is unknown."
      +}
    • changedOutput schema / properties / recordings / items / required
      Previous value: -[
      -  "artifact_id",
      -  "title",
      -  "duration_seconds",
      -  "project_id"
      -]New value: +[
      +  "artifact_id",
      +  "title",
      +  "duration_seconds",
      +  "created_at",
      +  "project_id"
      +]
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior. The description adds useful context beyond them: results are ordered most recently recorded first, each entry has a recording date and artifact_id, and an empty list means no recordings were shared yet.

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?

Three short sentences, front-loaded with the main purpose, followed by the prerequisite and the ordering/empty-list facts. No filler or redundancy.

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 an output schema and rich annotations already present, the description supplies everything an agent needs: purpose, required input source, result ordering, return-shape hint (date plus artifact_id), and empty-result meaning.

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

Parameters3/5

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

Schema coverage is 100% and the schema already documents the course_id provenance from search-courses, the numeric-string acceptance, and the limit range. The description repeats the course_id source but adds no new meaning for limit, so baseline 3 applies.

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?

States a specific verb and resource ('List public class recordings') plus the distinguishing scope detail that they are lecture audio with transcripts shared by students for a course. This cleanly separates it from siblings like get-course-syllabus or search-documents.

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?

Explicitly says to pass course_id from search-courses, giving the agent the prerequisite flow. It also explains the empty-list case, though it does not name an alternative tool or state when not to use this one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources