Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

delete_module_item

DestructiveIdempotent

Remove a module item from a Canvas course without deleting the underlying content. Preview first, then confirm to unlink.

Instructions

Remove an item from a module. Two-step: preview first, then confirm with the token.

IMPORTANT: Only unlinks the item from the module. The actual content (page, assignment, etc.) is NOT deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesItem ID to remove
module_idYesModule ID containing the item
course_identifierYesCourse code or Canvas ID
confirmation_tokenNoToken from the preview call; omit to preview

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / confirmation_token
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Token from the preview call; omit to preview"
+}
  2. 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
  3. 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 / item_id / description
      Added value: +"Item ID to remove"
    • 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"
    • removedInput schema / title
      Removed value: -"delete_module_itemArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"delete_module_itemOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Addedv1.3.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint/idempotentHint annotations, the description explains the two-step confirmation flow and precisely what gets affected: the module link only, not the underlying content. This materially reduces the risk of an agent invoking a destructive action carelessly and adds real value over the annotations alone.

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?

Three short, scannable sentences: the action, the workflow requirement, and the critical caveat. Every sentence earns its place without redundancy or filler.

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

Completeness4/5

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

For a destructive two-step tool with full schema coverage, the description gives the essential protocol and side-effect scope. It does not describe the preview response shape or explicitly point to an alternative for deleting underlying content, but those are minor given the schema and annotations.

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%, and the schema already documents each parameter, including the confirmation_token's 'Token from the preview call; omit to preview' semantics. The description's mention of the token flow restates schema information rather than adding new parameter-level meaning.

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?

States a specific verb and resource: 'Remove an item from a module.' The clarification that it only unlinks and does not delete the actual content distinguishes it from content-deleting tools like delete_assignment_with_confirmation and from delete_module.

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?

Provides an explicit procedure: 'preview first, then confirm with the token.' It also clarifies scope by noting the content is NOT deleted, signaling when this tool is insufficient. It does not name a specific alternative tool for actually deleting content, so it stops short of full routing guidance.

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

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