Canvas MCP Server

Overview Schema Related Servers Score Discussions

update_module_item

DestructiveIdempotent

Update an existing Canvas course module item by changing its title, position, indent, publication status, external URL, or completion requirements. Move the item to another module when needed.

Instructions

Update an existing module item.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

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

B3.3/5.0

Behavior2/5

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

The description adds no behavioral details beyond the annotations. While annotations indicate idempotent and destructive behavior, the description does not explain what happens during the update (e.g., partial updates, return value, side effects). Thus it offers minimal additional transparency.

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 concise sentence, directly stating the purpose without unnecessary words or redundancy. It is efficiently structured.

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?

The description is minimal but covers the core action. However, it omits details such as whether unspecified fields remain unchanged, whether the operation returns the updated item, or any error conditions. Given the tool's simplicity, this is adequate but not fully complete.

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?

The schema already provides descriptions for all 12 parameters, and the tool description does not add any interaction context or meaning beyond those individual descriptions. Since schema coverage is 100%, the baseline is 3; no added value from the description.

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 clearly states the action (update) and the resource (module item), distinguishing it from sibling tools like create_module_item or delete_module_item. It is unambiguous and specific.

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 description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., needing module_id and item_id) or expected outcomes. It is a bare statement with no contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server