Canvas LMS MCP Server

Create Page

create_page

Destructive

Create a new wiki page in a Canvas course by providing the course ID and title, with optional HTML body, publishing status, and editing roles.

Instructions

Create a new wiki page in a course.

Input Schema

TableJSON 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

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

A4/5.0

Behavior3/5

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

The annotations already provide openWorldHint=true and destructiveHint=true, signaling this tool may affect external state and requires caution. The description adds only that the page is 'new', implying creation rather than editing an existing page. It does not disclose behaviors like duplicate-title handling, authorization requirements, or whether publishing is affected. With annotations already carrying the main safety signals, the description adds some but limited behavioral value.

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?

The description is a single, front-loaded sentence that says exactly what the tool does. There is no fluff or redundant wording, and every part of the 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?

Given the presence of a complete input schema, annotations, and an output schema, the description is mostly sufficient for correct tool selection and invocation. It might be slightly stronger with an explicit note about page uniqueness or permission requirements, but these are not necessary for the agent to fill required parameters and call the tool.

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?

The input schema covers all 5 parameters with descriptions, and schema description coverage is 100%, so the description does not need to compensate for missing docs. The description itself adds no parameter detail beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

The description states a specific verb and resource ('create a new wiki page') and scopes it to a course, which clearly distinguishes it from siblings like list_pages, get_page, update_page, and delete_page. It is not a tautology because it adds the 'in a course' context and 'new' identifies creation rather than modification.

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?

The description gives clear context: use this when you need to create a new wiki page in a course. It does not explicitly exclude alternatives or mention prerequisites, but the creation verb and 'new' imply the when-to-use condition. There are no misleading hints about when to choose this over a sibling.

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

Deploy Server