Skip to main content
Glama

List course lessons

list_course_lessons
Read-onlyIdempotent

Retrieve course lessons from a Circle community. Supports pagination, filtering by status, space, or section, and sorting.

Instructions

List course lessons. Reads community data. Supports bounded all_pages; every page counts against the API quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_course_lessons"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
sortNoSorting parameters (sort by name in ascending order, name in descending order, and by newest. Default is oldest)
statusNoStatus
accountNoNamed private Circle account; selects credentials, not a remote community ID.
per_pageNoNumber of records per page
space_idNoSpace ID
all_pagesNoRead bounded page/per_page pages; each request consumes API quota. Not a snapshot or guaranteed complete backup.
max_itemsNoMaximum returned records with all_pages=true, default 1000. At most 100 requests; output includes continuation state.
section_idNoSection ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, covering the safety profile. The description adds that it 'reads community data' and warns that every page consumes quota, which is useful context, but the quota/all_pages details largely restate the schema parameter descriptions rather than adding new behavioral nuance.

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?

Three short sentences with the purpose front-loaded and no wasted filler. The opening sentence only restates the title, which is a minor redundancy but the rest is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering the safety profile and the schema at 100% coverage, the description is roughly adequate for a 9-param read tool and no output schema exists. It still omits default pagination behavior and the relationship to sibling list/get tools, leaving the picture incomplete.

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 description coverage is 100%, so all nine parameters are already documented in the schema. The description adds no parameter semantics beyond what is provided there, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('List course lessons'), which is clearly distinct from the singular get_course_lesson sibling. However, it does not explicitly differentiate itself from related list tools like list_course_sections, so it stops short of full sibling routing.

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

Usage Guidelines2/5

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

The description notes quota behavior for all_pages but gives no guidance on when to use this tool versus alternatives such as get_course_lesson or list_course_sections. No prerequisites or exclusions are stated.

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

Deploy Server

Other Tools