Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Account Courses

list_account_courses
Read-only

List every course in a Canvas account, optionally filtered by search_term matching course name or course code. Fetches every page (100 per request) and fails with a 'Results are incomplete' error instead of silently truncating.

Instructions

List every course in a Canvas account, optionally filtered by search_term matching course name or course code. Fetches every page (100 per request) and fails with a 'Results are incomplete' error instead of silently truncating. Use list_sub_accounts first if you want one sub-account's courses rather than this account's own, and list_courses instead for the courses the authenticated user is enrolled in or can access, rather than a full account inventory. Requires an admin role on the account.

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": {
      "account_id": "<account_id>"
    },
    "name": "list_account_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesThe Canvas account ID
search_termNoSearch courses by name or course code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.15
    • addedInput schema / properties / account_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / account_id / type
      Removed value: -"number"
  2. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.18.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly and openWorld, so the description adds real behavioral value: it discloses pagination chunk size (100 per request), that it auto-fetches all pages, and that it errors with 'Results are incomplete' rather than truncating silently. It also states the admin role requirement — exactly the operational detail an agent needs.

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?

Four tightly-packed sentences, front-loaded with the core action and filter, followed by pagination behavior, sibling routing, and the auth prerequisite. No filler; every sentence carries actionable information.

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 2-param read-only list tool with no output schema, the description covers scope, filtering, pagination/truncation semantics, admin requirement, and alternatives to sibling tools. Nothing essential to correct invocation 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 100%, so both parameters are already documented. The description restates that search_term matches course name or code (essentially the schema wording) and clarifies that account_id scopes to this account's own courses, a minor addition. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (List) and resource (courses in a Canvas account) with scope and optional filter. It names the siblings it is NOT (list_sub_accounts, list_courses), so an agent can distinguish it from the crowded catalog without opening any schema.

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?

Explicit routing: use list_sub_accounts for a sub-account's courses, use list_courses for the authenticated user's accessible courses, and this tool for a full account inventory. The admin-role prerequisite is also stated, leaving nothing to inference.

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