Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Local Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List Module Items

list_module_items
Read-onlyIdempotent

List a Canvas module's items—assignments, pages, files, quizzes, links—with each one's completion requirement and whether you met it. Read-only; find module IDs with list_modules.

Instructions

List the items in a module (assignments, pages, files, quizzes, links) with each one's completion requirement and whether you met it. Read-only. Use list_modules to find module IDs.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items to return. Smaller is faster.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
module_idYesModule ID (numeric string). Get it from list_modules.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • 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."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • changedInput schema / properties / module_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Module ID (numeric string). Get it from list_modules."
  2. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

While annotations cover safety, the description provides crucial behavioral context by stating that the returned items include 'completion requirement and whether you met it.' This defines the specific data the agent can work with.

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 definition is brief, efficient, and front-loaded. The core function and output description are provided before the usage guidance.

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?

Given the input schema is 100% documented, the description successfully covers all critical operational details: the types of items listed, the required IDs, and the prerequisite step of finding module IDs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds semantic meaning by explaining the trade-off for the 'limit' parameter: 'Smaller is faster.' It also provides operational context for the required IDs, though the schema is already 100% covered.

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?

The description explicitly states the resource being targeted (items in a module) and the type of content listed (assignments, pages, files, quizzes, links). It is highly specific and distinguishes itself from general content listing tools.

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?

It provides strong usage guidance by advising the agent to use `list_modules` to acquire the `module_id`. This prevents the agent from failing due to missing IDs.

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