Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Course Files

list_course_files
Read-only

Retrieve and filter files from a Canvas course by name, with optional sorting by size, date, or type. Use course code or ID to list course materials.

Instructions

List files in a Canvas course with optional search.

Input Schema

NameRequiredDescriptionDefault
sortNoSort field: name, size, created_at, updated_at, content_type (default: updated_at)updated_at
orderNo"asc" or "desc" (default: desc)desc
search_termNoFilter files by name
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / order / description
      Added value: +"\"asc\" or \"desc\" (default: desc)"
    • removedInput schema / properties / order / title
      Removed value: -"Order"
    • addedInput schema / properties / search_term / description
      Added value: +"Filter files by name"
    • removedInput schema / properties / search_term / title
      Removed value: -"Search Term"
    • addedInput schema / properties / sort / description
      Added value: +"Sort field: name, size, created_at, updated_at, content_type (default: updated_at)"
    • removedInput schema / properties / sort / title
      Removed value: -"Sort"
    • removedInput schema / title
      Removed value: -"list_course_filesArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"list_course_filesOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.3.0

TDQS

B3.1/5.0
Behavior2/5

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

The readOnlyHint annotation already tells the agent this is a safe read operation. The description adds only that files are course-scoped and search is optional, but does not disclose pagination behavior, return size, permission requirements, or what file types are included.

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?

The description is a single efficient sentence with no wasted words. The core operation and the optional search feature are front-loaded and easy to parse.

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?

For a simple read-only list tool with full schema coverage and a readOnlyHint annotation, the essential information is present. However, it omits routing guidance against similar file-listing/reading tools and does not describe the result shape, leaving some contextual gaps.

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 four parameters are already well documented in the schema. The description only echoes the optional search behavior, matching the baseline of 3 for a description that does not meaningfully extend the schema's parameter semantics.

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 gives a specific verb and resource: "List files in a Canvas course." It clearly identifies the operation and scope, though it does not explicitly distinguish this tool from siblings like list_group_files or download_course_file.

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 phrase "with optional search" hints at when the search parameter is useful, but there is no explicit guidance on when to use this tool versus alternatives such as list_group_files or read_course_file. 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