Skip to main content
Glama
Fireiscoolsolo

Canvas LMS MCP – Local Edition

by Fireiscoolsolo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get Page Revision

get_page_revision
Read-onlyIdempotent

Retrieve a course page's content as it appeared at a specific past revision, including editor and date. Use revision numbers from list_page_revisions to review page history; read-only.

Instructions

Get the content of a course page as it was at one past revision, with the editor and date. Read-only. The body is fenced as untrusted text. Use list_page_revisions to find revision numbers, and get_page_content for the current version. Canvas returns a permission error if page history is hidden from students.

Input Schema

NameRequiredDescriptionDefault
page_urlYesThe page's URL slug, e.g. "week-1-overview" (the last part of the page address). Get it from list_pages.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
revision_idYesRevision number of the page, from list_page_revisions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • addedInput schema / properties / page_url / description
      Added value: +"The page's URL slug, e.g. \"week-1-overview\" (the last part of the page address). Get it from list_pages."
    • changedInput schema / properties / revision_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Revision number of the page, from list_page_revisions."
  2. First observedv1.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safe-read profile, and the description adds value beyond them: the body is fenced as untrusted text (a real handling constraint for an agent) and Canvas returns a permission error if history is hidden. This is exactly the kind of context annotations cannot carry.

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?

Four tight sentences, front-loaded with purpose and return contents, followed by the safety note and routing alternatives. No wasted phrasing.

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?

No output schema exists, but the description states what comes back (content, editor, date), how to obtain inputs, and the failure condition. An agent has everything needed 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 coverage is 100% and each parameter already documents its origin (slug from list_pages, course_id from list_courses, revision_id from list_page_revisions). The description repeats the revision-number sourcing but adds no format or syntax detail beyond the schema, so baseline 3 applies.

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 with scope: 'Get the content of a course page as it was at one past revision.' It explicitly distinguishes itself from the current-version sibling (get_page_content) and from the revision enumerator (list_page_revisions).

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?

Names both alternatives and the condition for each: list_page_revisions to find revision numbers, get_page_content for the current version. It also flags the failure mode (permission error when page history is hidden).

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

Deploy Server

Other Tools