Canvas LMS MCP Server

Update Page

update_page

Destructive

Update an existing Canvas wiki page by changing its content, title, publishing status, or editing permissions. Specify course ID and page URL to locate the page.

Instructions

Update an existing wiki page.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	No	New HTML body content
`title`	No	New title for the page
`page_url`	Yes	The page URL slug
`course_id`	Yes	The Canvas course ID
`published`	No	Whether the page is published
`editing_roles`	No	Who can edit: "teachers", "students", "members", or "public"

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`body`	No
`title`	Yes
`page_id`	Yes
`published`	No
`created_at`	No
`updated_at`	No
`editing_roles`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.18.11Sep 10, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed1 schema field changedv1.18.9Sep 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "body": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "created_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "editing_roles": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "page_id": {
+      "type": "number"
+    },
+    "published": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "title": {
+      "type": "string"
+    },
+    "updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "page_id",
+    "url",
+    "title"
+  ],
+  "type": "object"
+}

First observedv1.18.0May 25, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations indicate destructiveHint=true, so the description must explain what destructive effects occur (e.g., overwrites existing content, may be irreversible). The description only says 'update,' which implies mutation but does not disclose consequences. No annotation contradiction, but significant gap.

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

Conciseness4/5

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

The description is a single clear sentence, appropriately terse. It lacks detail but is not verbose. Every word earns its place; no fluff.

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

Completeness2/5

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

This is a destructive mutation tool with an output schema, but the description provides only the bare minimum. It does not explain partial vs full updates, whether editing_roles can be changed, or any side effects. The agent lacks critical context to call 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 each parameter has a description. The tool description adds no extra meaning, but the schema already documents all parameters. Baseline 3 is appropriate because the description does not add value beyond the schema.

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

Purpose3/5

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

The description states a clear verb and resource ('Update an existing wiki page'), but it does not specify which fields can be updated or distinguish it from sibling tools like create_page and delete_page. It is minimally clear but lacks detail.

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 tool versus alternatives. For a mutation tool with siblings create_page and delete_page, an agent gets no context about whether updates are partial or full, or whether it requires an existing page.

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

Deploy Server