Canvas LMS MCP Server

Create Page

create_page

Destructive

Instructions

Create a new wiki page in a course with a title and optional HTML body, published state and editing_roles, and return the created page — including its url slug, used as page_url by get_page, update_page and delete_page. Not idempotent: each call creates another page; Canvas does not deduplicate by title, so check list_pages first to avoid creating a duplicate. Use update_page to edit an existing page instead of creating a new one, and create_module_item's page_url parameter (with type Page) to place this page inside a module. Requires permission to manage wiki content in the course.

Input Schema

Name	Required	Description
`body`	No	HTML body content of the page
`title`	Yes	Title of the page
`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

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

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the non-idempotent write semantics, that Canvas does not deduplicate by title, and the required permission to manage wiki content. It also names the returned url slug that other tools depend on, which is not derivable from destructiveHint/openWorldHint.

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?

Front-loaded with the core action, then the idempotency caveat, then alternatives, then the permission note — a sensible order with no filler. It is dense but each clause contributes; the single very long sentence slightly hurts scannability.

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

Completeness5/5

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

Covers everything an agent needs: prerequisites, duplicate risk, sibling routing, and downstream use of the returned slug. With an output schema present, it correctly does not waste space narrating the full return shape.

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 parameters are already documented. The description restates the parameter set (title, optional HTML body, published state, editing_roles) without adding format or validation guidance, so it earns only 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 verb and resource ('Create a new wiki page in a course') plus the key fields supplied and the created artifact returned. It explicitly names the sibling operations (get_page, update_page, delete_page, list_pages, create_module_item) so it is distinguishable without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not ('Use update_page to edit an existing page instead of creating a new one') and a concrete duplicate-avoidance path ('check list_pages first'). It also tells the agent how a follow-on tool consumes the result (create_module_item's page_url with type Page).

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

Deploy Server