Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Download All Course Files

download_all_course_files
Idempotent

Download every accessible file from a Canvas course to local disk, with optional MIME-type filters and a max_files limit (default 50).

Instructions

Download every file you can access in a course to local disk, up to max_files (default 50). Writes local files only; nothing changes in Canvas. Can take many requests and a lot of disk space; use download_file for one file.

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": "download_all_course_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
dest_dirNoFolder to save into: the server's download folder (CANVAS_DOWNLOAD_DIR) or a folder inside it, such as "week1". Anywhere else is refused. Leave it out to use the download folder itself.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
max_filesNoDefault 50
content_typesNoOptional MIME types to include, e.g. ["application/pdf"]. Omit for every file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • changedInput schema / properties / dest_dir / description
      Previous value: -"Local folder to save into. Defaults to the server's download folder (CANVAS_DOWNLOAD_DIR)."New value: +"Folder to save into: the server's download folder (CANVAS_DOWNLOAD_DIR) or a folder inside it, such as \"week1\". Anywhere else is refused. Leave it out to use the download folder itself."
  2. Changed3 schema fields changedv1.1.3
    • addedInput schema / properties / content_types / description
      Added value: +"Optional MIME types to include, e.g. [\"application/pdf\"]. Omit for every file."
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • addedInput schema / properties / dest_dir / description
      Added value: +"Local folder to save into. Defaults to the server's download folder (CANVAS_DOWNLOAD_DIR)."
  3. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds real value beyond the annotations: it clarifies that despite readOnlyHint=false no Canvas state is mutated ("Writes local files only; nothing changes in Canvas") and warns about request volume and disk consumption. It does not disclose what happens on partial failure, whether existing files are overwritten, or whether subfolders are recursed, which matters for a bulk write.

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 action and scope, then the side-effect clarification, then the cost warning and sibling pointer. Nothing is redundant or buries the lede.

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?

For a bulk local-write tool with no output schema, the description covers scope, side effects, cost, and the single-file alternative. The remaining gap is return behavior on partial failure or skipped files, which an agent would want given no output schema documents it.

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 the schema already documents dest_dir's sandbox restriction, course_id's source, content_types' MIME filtering, and max_files' default. The description's only parameter nod is restating the max_files default, adding no new meaning; 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 ("Download every file you can access in a course to local disk") plus the scoping parameter max_files and its default. The closing clause explicitly contrasts it with the sibling download_file, so an agent can route between the two without opening either schema.

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?

Names the alternative tool (download_file) and the condition that selects it ("for one file"). It also implies a caution case via "Can take many requests and a lot of disk space," but gives no explicit threshold for when the bulk operation is inappropriate or what to do if it fails partway.

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