Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Module Items

list_module_items
Read-only

Lists items within a specific Canvas course module, including pages and optional content details, using a course identifier and module ID.

Instructions

List items within a specific module, including pages.

Input Schema

NameRequiredDescriptionDefault
module_idYesThe module ID
course_identifierYesCourse code or Canvas ID
include_content_detailsNoInclude additional content details (default: True)

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. Changed11 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 / include_content_details / description
      Added value: +"Include additional content details (default: True)"
    • removedInput schema / properties / include_content_details / title
      Removed value: -"Include Content Details"
    • addedInput schema / properties / module_id / description
      Added value: +"The module ID"
    • removedInput schema / properties / module_id / title
      Removed value: -"Module Id"
    • removedInput schema / title
      Removed value: -"list_module_itemsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"list_module_itemsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"list_module_itemsArguments"
  4. First observed

TDQS

C2.9/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read. The only added behavioral signal is 'including pages', a small hint about result composition; nothing about pagination, ordering, or what happens when include_content_details is toggled off.

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?

A single front-loaded sentence with no filler. It is efficient, though it borders on under-specified for a tool that can return heterogeneous item types.

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 tool with full schema coverage, annotations, and no output schema, the description is minimally adequate. It never clarifies what an 'item' can be (assignment, quiz, file, page, external URL) or how results are ordered, which matters for interpreting the output.

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 three parameters (module_id, course_identifier, include_content_details) are documented in the schema itself. The description adds no extra meaning about accepted identifier forms or the effect of the details flag, so the baseline 3 applies.

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 (List) and resource (items within a module), and adds that pages are included among the results. It does not distinguish itself from neighbors like list_modules, get_course_structure, or list_pages, so an agent must infer the boundary from the name alone.

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?

There is no guidance on when to choose this over list_modules (parent listing) or get_course_content_overview / list_pages (other ways to see module contents). 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