Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Page

create_page
Destructive

Create a new page in a Canvas course, published by default or saved as a draft, with optional front-page status and editing permissions.

Instructions

Create a page in a Canvas course.

Pages are published by default, so the page is visible to students on creation (subject to any module or access restrictions); pass published=False to create a draft.

Input Schema

NameRequiredDescriptionDefault
bodyYesHTML content for the page
titleYesPage title
publishedNoWhether to publish (default: True)
front_pageNoWhether to set as front page (default: False)
editing_rolesNoWho can edit (default: "teachers")teachers
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. Changed17 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / body / description
      Added value: +"HTML content for the page"
    • removedInput schema / properties / body / title
      Removed value: -"Body"
    • 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 / editing_roles / description
      Added value: +"Who can edit (default: \"teachers\")"
    • removedInput schema / properties / editing_roles / title
      Removed value: -"Editing Roles"
    • addedInput schema / properties / front_page / description
      Added value: +"Whether to set as front page (default: False)"
    • removedInput schema / properties / front_page / title
      Removed value: -"Front Page"
    • addedInput schema / properties / published / description
      Added value: +"Whether to publish (default: True)"
    • removedInput schema / properties / published / title
      Removed value: -"Published"
    • addedInput schema / properties / title / description
      Added value: +"Page title"
    • removedInput schema / properties / title / title
      Removed value: -"Title"
    • removedInput schema / title
      Removed value: -"create_pageArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"create_pageOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"create_pageArguments"
  4. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Adds real value beyond the annotations by disclosing that pages publish by default and are student-visible on creation, subject to module/access restrictions — a side effect an agent must know about. However, with destructiveHint=true declared, the description says nothing about the destructive/mutation implications, permission requirements, or whether a duplicate title overwrites anything.

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?

Two short sentences with the core action front-loaded and the non-obvious default immediately after. No filler; could be tightened slightly but is well-structured.

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

Completeness3/5

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

For a 6-param mutation tool with no output schema, the description covers the most important behavior (default publication) but omits permission requirements, what `front_page=True` displaces, and what the returned page reference looks like. Adequate but with clear gaps.

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%, so the schema already documents all six parameters. The description adds contextual meaning for `published` (default visibility to students) beyond the schema's 'Whether to publish (default: True)', but says nothing about `front_page` or `editing_roles`, which carry non-obvious course-wide effects.

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?

States a specific verb and resource ('Create a page in a Canvas course'), which clearly separates it from siblings like edit_page_content, update_page_settings, and delete_page. It doesn't explicitly name a sibling boundary, but the create vs. modify distinction is unambiguous.

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?

Gives an actionable usage hint ('pass published=False to create a draft') but does not say when to use this versus edit_page_content or update_page_settings, nor any prerequisites (e.g., teacher role needed to create pages in a course).

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