Canvas LMS MCP Server

Get Page

get_page

Read-only

Retrieve a specific Canvas wiki page by its URL slug and course ID. Provide the course_id and page_url to fetch page details.

Instructions

Get a single wiki page by its URL slug.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page_url`	Yes	The page URL slug (e.g. "welcome-page")
`course_id`	Yes	The Canvas course ID

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

A3.9/5.0

Behavior3/5

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

Annotations already carry readOnlyHint=true, so the read-only nature is established. The description adds no additional behavioral detail such as page-not-found behavior, visibility restrictions, or what happens when the page is missing; it simply restates the read operation.

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?

One sentence, front-loaded, and free of filler. It communicates the operation and the identifying parameter without wasted words.

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?

For a simple two-parameter, read-only getter with full schema coverage, an output schema, and safety annotations, this description is sufficient. No critical information an agent needs to invoke it correctly is missing.

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%: both page_url and course_id already have clear descriptions and an example. The description only restates the page_url concept and does not add meaning beyond what the schema already provides.

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 clear verb ('Get'), the resource ('single wiki page'), and the key lookup key ('URL slug'). The word 'single' differentiates it from list_pages, and the slug requirement differentiates it from page-by-id or content tools.

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

Usage Guidelines3/5

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

The description implies the caller must already know the page's URL slug, but it does not explicitly say when to choose this tool over list_pages or how to discover slugs. Usage is implied rather than stated, with no explicit exclusions or alternatives.

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

Deploy Server