Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Module Item

create_module_item
Destructive

Add an item (Assignment, Page, Quiz, File, Discussion, ExternalUrl, ExternalTool, SubHeader) to a module.

Instructions

Add an item (Assignment, Page, Quiz, File, Discussion, ExternalUrl, ExternalTool, SubHeader) to a module.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesType of content to add
titleYesTitle of the module item
page_urlNoPage URL slug (required for Page items, which are addressed by slug, not ID)
positionNoPosition within the module
course_idYesThe Canvas course ID
module_idYesThe Canvas module ID
content_idNoCanvas ID of the content (required for File, Discussion, Assignment, Quiz)
external_urlNoURL for ExternalUrl or ExternalTool items

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.18.15
    • addedInput schema / properties / content_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / content_id / description
      Previous value: -"Canvas ID of the content (required for File, Page, Discussion, Assignment, Quiz)"New value: +"Canvas ID of the content (required for File, Discussion, Assignment, Quiz)"
    • removedInput schema / properties / content_id / type
      Removed value: -"number"
    • addedInput schema / properties / course_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / course_id / type
      Removed value: -"number"
    • addedInput schema / properties / module_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / module_id / type
      Removed value: -"number"
    • addedInput schema / properties / page_url
      Added value: +{
+  "description": "Page URL slug (required for Page items, which are addressed by slug, not ID)",
+  "type": "string"
+}
  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

C2.9/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true and destructiveHint=true, so the mutation profile is covered. The description adds essentially nothing beyond that: no side effects, no effect on module ordering/positions, no note that unpublishing or permissions may be required. No contradiction, but minimal added value.

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 the parenthetical type list duplicates the schema enum and could have carried conditional-parameter guidance instead.

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 mutation tool with no output schema and full parameter documentation, the description is minimally adequate. It omits the conditional required-field logic per item type (which types need page_url vs content_id vs external_url), leaving the agent to reconstruct that from schema prose.

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 every parameter including the conditional ones (page_url for Page, content_id for File/Discussion/Assignment/Quiz, external_url for external items). The description merely restates the type enum, adding no meaning beyond the schema. Baseline 3.

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 ('Add') and resource ('item ... to a module'), and enumerates the accepted item types. It is distinguishable from siblings like create_module and update_module_item, though it never names them explicitly.

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 use this versus update_module_item or create_module, nor any prerequisite (e.g. that the target module must already exist). The agent must infer usage entirely from the name and siblings.

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