Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

update_page_settings

Destructive

Change a Canvas page's settings—publish status, front page assignment, editing roles, or update notifications—without modifying its content.

Instructions

Update settings for an existing page (without changing content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publishedNoTrue to publish, False to unpublish
front_pageNoTrue to make this the course front page
editing_rolesNoOne of: teachers, students, members, public
page_url_or_idYesPage URL slug or page ID
notify_of_updateNoSave-time action, NOT a persisted setting. Asks Canvas to notify course participants about THIS edit. Canvas never returns the flag, so this tool cannot confirm a notification was sent and the Canvas UI checkbox will always look unchecked afterward. Has no effect on an unpublished page or a page under a minute old.
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  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 / 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: +"One of: teachers, students, members, public"
    • removedInput schema / properties / editing_roles / title
      Removed value: -"Editing Roles"
    • addedInput schema / properties / front_page / description
      Added value: +"True to make this the course front page"
    • removedInput schema / properties / front_page / title
      Removed value: -"Front Page"
    • addedInput schema / properties / notify_of_update / description
      Added value: +"Save-time action, NOT a persisted setting. Asks\nCanvas to notify course participants about THIS edit. Canvas\nnever returns the flag, so this tool cannot confirm a\nnotification was sent and the Canvas UI checkbox will always\nlook unchecked afterward. Has no effect on an unpublished page\nor a page under a minute old."
    • removedInput schema / properties / notify_of_update / title
      Removed value: -"Notify Of Update"
    • 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"
    • addedInput schema / properties / published / description
      Added value: +"True to publish, False to unpublish"
    • removedInput schema / properties / published / title
      Removed value: -"Published"
    • removedInput schema / title
      Removed value: -"update_page_settingsArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"update_page_settingsOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.3.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already include destructiveHint=true, so the agent knows this is a mutation with potential destructive effects. The description adds the useful boundary that content is not changed, but it does not disclose what makes it destructive (e.g., unpublishing a page, changing front page, altering editing roles). The schema carries some of this burden, but the description itself could add more context.

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 entire description is one concise, front-loaded sentence. Every word earns its place by clarifying both the action and the scope (existing page, no content change). No fluff or redundancy.

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 mutation tool with 6 parameters and no output schema, the description is somewhat sparse. It does not mention what the tool returns, potential failure modes, or the significance of the destructive hint. However, the rich schema and annotations partially compensate, making this an adequate but not complete description.

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 does not add any parameter-specific semantics beyond the schema, except implicitly clarifying that all parameters are settings-related (not content), which is a minor addition.

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 uses a specific verb ('Update') and resource ('settings for an existing page') and explicitly clarifies what it does NOT do ('without changing content'). This clearly distinguishes it from sibling tools like edit_page_content and delete_page.

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 phrase 'without changing content' implies the tool is for settings-only updates, providing clear context for when to use it. However, it does not explicitly name alternatives or state when NOT to use it, so it's one step below explicit usage guidelines.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server