Canvas LMS MCP Server

Update Page

update_page

Destructive

Update an existing wiki 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.

Changed3 schema fields changedv1.18.15Oct 14, 2026

addedInput schema / properties / course_id / anyOf

Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]

removedInput schema / properties / course_id / type
```
Removed value: -"number"
```

changedOutput schema / properties / page_id / type

Previous value: -"number"New value: +[
+  "number",
+  "string"
+]

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.9/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered. The description adds no behavioral context beyond the verb 'update'—it does not say that existing page content may be overwritten, what permissions are required, or what happens to unpublished pages.

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?

A single sentence with no wasted words and the action is front-loaded. It is appropriately concise, though its extreme brevity leaves little room for structural guidance.

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 tool is a mutation operation, but annotations cover the destructive/open-world profile and an output schema exists for return values. With 100% schema coverage, the structured data carries most requirements; the description is minimally viable but does not say enough about scope or prerequisites to be more than adequate.

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 all six parameters are documented in the input schema. The description adds no parameter-level meaning beyond that baseline, which is acceptable when the schema does the work.

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 (update) and resource (existing wiki page), making it clear this modifies rather than creates, deletes, or reads a page. It does not explicitly distinguish itself from sibling tools like create_page or delete_page, but the purpose is unambiguous.

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 gives no when-to-use guidance, prerequisites, or alternatives. It implies use when modifying an existing page, but does not say when to choose this over create_page, update_discussion, or other update tools.

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

Deploy Server