Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Bulk Update Pages

bulk_update_pages
Destructive

Update settings for multiple Canvas pages at once, including publishing status and editing roles; page names and content are unchanged.

Instructions

Update settings for multiple pages at once.

Settings only — this tool cannot rename pages or change page content. Use edit_page_content to change a page's body.

Input Schema

NameRequiredDescriptionDefault
page_urlsYesComma-separated list of page URL slugs
publishedNoTrue to publish all, False to unpublish all
editing_rolesNoOne of: teachers, students, members, public
notify_of_updateNoSave-time action, NOT a persisted setting. Asks Canvas to notify course participants about these edits. Canvas never returns the flag, so this tool cannot confirm any notification was sent. Has no effect on unpublished pages.
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. Changed15 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 / notify_of_update / description
      Added value: +"Save-time action, NOT a persisted setting. Asks\nCanvas to notify course participants about these edits. Canvas\nnever returns the flag, so this tool cannot confirm any\nnotification was sent. Has no effect on unpublished pages."
    • removedInput schema / properties / notify_of_update / title
      Removed value: -"Notify Of Update"
    • addedInput schema / properties / page_urls / description
      Added value: +"Comma-separated list of page URL slugs"
    • removedInput schema / properties / page_urls / title
      Removed value: -"Page Urls"
    • addedInput schema / properties / published / description
      Added value: +"True to publish all, False to unpublish all"
    • removedInput schema / properties / published / title
      Removed value: -"Published"
    • removedInput schema / title
      Removed value: -"bulk_update_pagesArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"bulk_update_pagesOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Addedv1.3.0

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=false. The description adds useful behavioral scope beyond that by limiting the tool to settings only and warning that names and content cannot be changed, though it does not explain the destructive nature of bulk settings overwrites or partial-failure behavior.

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 description is three short sentences, front-loads the main purpose, immediately states the key limitation, and then names the relevant alternative. Every sentence earns its place.

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 bulk destructive settings tool with a fully described input schema and no output schema, the description covers purpose, scope limits, and the content-editing alternative. It could say more about destructive bulk behavior or what happens on partial failures, but the essential selection context is present.

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 schema already documents page_urls, published, editing_roles, notify_of_update, and course_identifier. The description adds no parameter-level detail beyond the multi-page scope, so it appropriately sits at the baseline when the schema does the heavy lifting.

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 states a specific verb and resource: updating settings for multiple pages at once. It also distinguishes this tool from edit_page_content, which is the sibling for changing page bodies, so an agent can identify its role without opening the schema.

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 description makes the multi-page scope explicit and gives a clear exclusion: it cannot rename pages or change page content, and directs body changes to edit_page_content. It does not explicitly contrast with update_page_settings for single-page updates, so it stops just short of full alternative routing.

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