Skip to main content
Glama

List courses

list_courses
Read-onlyIdempotent

Lists Academy courses with selectable sorting and cursor pagination. Render every returned course title as Title, never as bare text followed by a separate URL. Omit cursor initially. To continue, pass the previous response next_cursor as cursor with the same query and state. There is no page-number parameter: page_size is the number of courses returned in one request.

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_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoupdated_desc
queryNoOptional case-insensitive partial match against the displayed title and internal name.
stateNoOptional course-state filter. Keep it unchanged while following a cursor.
cursorNoOmit for the first request. For the next batch, copy the previous response next_cursor.
page_sizeNoMaximum courses in this response, not a page number. For “show 2 courses”, use 2.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description needn't restate safety. It does add real value by disclosing cursor-based paging, the absence of page numbers, and the existence of a next_cursor in the response. It says nothing about ordering guarantees, total counts, or what happens when a cursor is stale.

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?

Front-loaded with the purpose in the first sentence, then pagination mechanics; no filler sentences. The markdown rendering instruction is a formatting rule rather than tool semantics, which slightly interrupts the flow but is still short and actionable.

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

Completeness4/5

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

With no output schema, the description sensibly covers the response's relevant shape (course titles, open_url, next_cursor) and how to consume it. Sort behavior and error conditions remain undocumented, but nothing critical for a correct call is missing.

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 80%, so the baseline is 3; the description mostly restates what the schema already says ('page_size is the number of courses returned in one request', 'omit cursor initially'). The useful addition is the instruction to hold query and state constant across cursor pages, but sort semantics are left entirely to the enum.

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?

States a specific verb+resource ('Lists Academy courses') and adds the scoping traits (sorting, cursor pagination). It is clearly the enumeration tool rather than the single-course readers like get_course_draft, though it never names a sibling explicitly.

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?

Gives operational when-to guidance for pagination: omit cursor on the first request, pass the previous next_cursor with the same query and state to continue. It stops short of saying when to prefer this over alternatives such as list_collections or how to combine filters across tools.

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