Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Page

delete_page
DestructiveIdempotent

Deletes a Canvas course page using a two-step preview and confirmation token, with optional exact title matching to prevent accidental removal.

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

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.

  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/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds real value beyond that: the mandatory preview/confirm token flow and the caveat that a recycle-bin copy may exist depending on admin settings, which tempers the word "Permanent." It does not mention permission requirements or what the preview returns.

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, front-loaded with the action and the two-step requirement, with the permanence caveat second. Nothing is wasted and no filler precedes the operative instruction.

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 mutation with no output schema, the description covers the critical unknowns: the confirmation flow and the true extent of permanence. It leaves auth/permission expectations and preview-call output unclear, which is a minor but real gap.

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 all four parameters. The description reinforces that confirmation_token comes from the preview call, but says nothing about require_title_match, the key safety parameter. Baseline 3 applies when the schema carries the detail.

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 and resource ("Delete a page") that is unambiguous against page siblings like create_page, edit_page_content, and update_page_settings. It does not explicitly name those siblings, so it falls short of the 5 mark.

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?

"Two-step: preview first, then confirm with the token" gives concrete invocation guidance and a clear order of operations. It does not say when deletion is the right choice versus alternatives such as update_page_settings or bulk_update_pages, so no exclusion guidance.

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