Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Page Content

get_page_content
Read-only

Retrieve a Canvas page's full HTML content and an inventory of embedded media sources by course and page identifier for explicit reporting.

Instructions

Get the full content body of a specific page.

Returns the page's raw HTML body untruncated, followed by an inventory of any embedded media (images, videos, iframes) with their source URLs, so media is reported explicitly rather than left for the reader to spot in the markup.

Input Schema

NameRequiredDescriptionDefault
page_url_or_idYesPage URL slug or page ID
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed9 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / page_url_or_id / description
      Added value: +"Page URL slug or page ID"
    • removedInput schema / properties / page_url_or_id / title
      Removed value: -"Page Url Or Id"
    • removedInput schema / title
      Removed value: -"get_page_contentArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"get_page_contentOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"get_page_contentArguments"
  4. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds useful return-behavior context: the HTML is untruncated and embedded media are inventoried with source URLs. It does not discuss errors, pagination, or permission requirements, but this is solid disclosure beyond the annotations.

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?

Two sentences, front-loaded with the core action, followed by only the return-format detail an agent needs. No wasted wording.

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?

For a read-only page-content tool with a fully described two-parameter schema, the description covers the essential return behavior, including raw HTML and media inventory. It could be more complete by distinguishing this from related page-detail tools, but it is largely 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 the baseline is 3. The description refers to a 'specific page' but adds no syntax, format, or lookup details beyond what the schema already says for page_url_or_id and course_identifier.

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?

The description states a specific verb and resource: getting the full content body of a specific page. It distinguishes the output from a metadata lookup by saying it returns the body and embedded media, but it never names or contrasts the sibling tools get_page_details or get_front_page.

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?

There is no explicit guidance on when to use this tool instead of get_page_details, get_front_page, or list_pages. The purpose implies the general use case, but the overlapping sibling names make the absence of routing guidance a real gap.

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