Canvas MCP Server

Overview Schema Source Related Servers Discussions Admin

Update Module Item

update_module_item

DestructiveIdempotent

Modify an existing Canvas module item's title, position, publication status, link, or completion requirements, or move it to another module.

Instructions

Update an existing module item.

Input Schema

Name	Required	Description
`title`	No	New item title
`indent`	No	New indentation level (0-4)
`item_id`	Yes	Item ID to update
`new_tab`	No	Open external links in new tab
`position`	No	New position within module
`module_id`	Yes	Module ID containing the item
`published`	No	Whether the item is published
`external_url`	No	New URL (ExternalUrl items only)
`course_identifier`	Yes	Course code or Canvas ID
`move_to_module_id`	No	Move item to a different module
`completion_requirement_type`	No	New completion type, or empty string to remove
`completion_requirement_min_score`	No	Minimum score (for min_score type)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.10.0Aug 20, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null

Changed29 schema fields changedv1.8.0Aug 10, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / completion_requirement_min_score / description
```
Added value: +"Minimum score (for min_score type)"
```
- removedInput schema / properties / completion_requirement_min_score / title
```
Removed value: -"Completion Requirement Min Score"
```
- addedInput schema / properties / completion_requirement_type / description
```
Added value: +"New completion type, or empty string to remove"
```
- removedInput schema / properties / completion_requirement_type / title
```
Removed value: -"Completion Requirement Type"
```
- 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 / external_url / description
```
Added value: +"New URL (ExternalUrl items only)"
```
- removedInput schema / properties / external_url / title
```
Removed value: -"External Url"
```
- addedInput schema / properties / indent / description
```
Added value: +"New indentation level (0-4)"
```
- removedInput schema / properties / indent / title
```
Removed value: -"Indent"
```
- addedInput schema / properties / item_id / description
```
Added value: +"Item ID to update"
```
- removedInput schema / properties / item_id / title
```
Removed value: -"Item Id"
```
- addedInput schema / properties / module_id / description
```
Added value: +"Module ID containing the item"
```
- removedInput schema / properties / module_id / title
```
Removed value: -"Module Id"
```
- addedInput schema / properties / move_to_module_id / description
```
Added value: +"Move item to a different module"
```
- removedInput schema / properties / move_to_module_id / title
```
Removed value: -"Move To Module Id"
```
- addedInput schema / properties / new_tab / description
```
Added value: +"Open external links in new tab"
```
- removedInput schema / properties / new_tab / title
```
Removed value: -"New Tab"
```
- addedInput schema / properties / position / description
```
Added value: +"New position within module"
```
- removedInput schema / properties / position / title
```
Removed value: -"Position"
```
- addedInput schema / properties / published / description
```
Added value: +"Whether the item is published"
```
- removedInput schema / properties / published / title
```
Removed value: -"Published"
```
- addedInput schema / properties / title / description
```
Added value: +"New item title"
```
- removedInput schema / properties / title / title
```
Removed value: -"Title"
```
- removedInput schema / title
```
Removed value: -"update_module_itemArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"update_module_itemOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```
Addedv1.3.0May 2, 2026

TDQS

D1.9/5.0

Behavior1/5

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

Annotations already flag idempotentHint=true and destructiveHint=true, yet the description adds nothing about them: it does not say that unspecified fields are left unchanged, that items can be moved across modules via move_to_module_id, or that updates can remove completion requirements. For a destructive 12-parameter mutation it discloses none of the behavior an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, but it is under-specified rather than concise: it is front-loaded with nothing useful beyond the title and gives the agent no anchor for a 12-parameter operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, 12-parameter mutation with no output schema and many interacting optional fields, one bare sentence leaves almost everything an agent must know before calling it unstated.

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 every parameter is documented in the schema itself; the description adds no additional meaning (e.g., partial-update semantics, how move_to_module_id interacts with module_id). Baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update an existing module item" only restates the tool name and title; it names a verb and resource but says nothing about what can be updated or how this differs from siblings such as update_module, add_module_item, or delete_module_item.

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 (whole module) or add/delete_module_item. The word "existing" faintly implies it is not for creation, but no alternatives or preconditions 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

Update Module Item

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools