Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

delete_page

DestructiveIdempotent

Permanently delete a Canvas course page after previewing and confirming with a token.

Instructions

Delete a page. Two-step: preview first, then confirm with the token.

Permanent — Canvas may retain a recycle-bin copy depending on admin settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_url_or_idYesPage URL slug or page ID to delete
course_identifierYesCourse code or Canvas ID
confirmation_tokenNoToken from the preview call; omit to preview
require_title_matchNoSafety check — only delete if page title matches exactly

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 / page_url_or_id / description
      Added value: +"Page URL slug or page ID to delete"
    • removedInput schema / properties / page_url_or_id / title
      Removed value: -"Page Url Or Id"
    • addedInput schema / properties / require_title_match / description
      Added value: +"Safety check — only delete if page title matches exactly"
    • removedInput schema / properties / require_title_match / title
      Removed value: -"Require Title Match"
    • removedInput schema / title
      Removed value: -"delete_pageArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"delete_pageOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Addedv1.3.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark the tool as destructive and idempotent, and the description adds valuable behavioral context: the two-step confirmation process and the fact that deletion is permanent but may still be recoverable via a recycle bin depending on admin settings. It goes beyond the annotations without contradicting them.

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?

Two short sentences with no filler. The key workflow is front-loaded, and the permanence warning follows naturally. Every sentence earns its place.

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, the description covers the workflow, permanence, and admin-dependent retention. The schema covers all parameters, and annotations cover safety traits. A small gap is the lack of detail about the preview response shape or error behavior, but the existing information is sufficient for most agents to invoke it correctly.

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 explains each parameter. The description adds no new parameter meaning beyond reiterating the confirmation-token workflow, which is already described in the schema. It does not significantly compensate beyond the baseline.

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 action and resource: 'Delete a page.' It also communicates the two-step preview/confirm workflow, which clearly distinguishes this from other delete tools targeting assignments or announcements. The description unambiguously identifies the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear workflow guidance: preview first, then confirm with the token, and omitting the token means preview. However, it does not explicitly mention when to choose this tool over alternatives such as delete_assignment_with_confirmation or delete_announcement_with_confirmation, so the usage context is implied rather than fully stated.

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