Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Create Content Migration

create_content_migration
Destructive

Preview a full course-copy migration, then confirm it with the returned token to execute the transfer between Canvas courses.

Instructions

Preview or confirm a full course-copy migration request.

The first call returns a target-occupancy preview and a short-lived token. A second call with the token and identical arguments requests the migration. Date shifting accepts either all four date fields or none.

Input Schema

NameRequiredDescriptionDefault
new_end_dateNoTarget course end date (ISO 8601), for date shifting
old_end_dateNoSource course end date (ISO 8601), for date shifting
new_start_dateNoTarget course start date (ISO 8601), for date shifting
old_start_dateNoSource course start date (ISO 8601), for date shifting
confirmation_tokenNoToken from the preview call; omit to preview
source_course_identifierYesCourse code or Canvas ID of the course to copy from; must differ from the target
target_course_identifierYesCourse code or Canvas ID of the course that receives the copied content

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.15.0
    • addedInput schema / properties / confirmation_token / description
      Added value: +"Token from the preview call; omit to preview"
    • addedInput schema / properties / new_end_date / description
      Added value: +"Target course end date (ISO 8601), for date shifting"
    • addedInput schema / properties / new_start_date / description
      Added value: +"Target course start date (ISO 8601), for date shifting"
    • addedInput schema / properties / old_end_date / description
      Added value: +"Source course end date (ISO 8601), for date shifting"
    • addedInput schema / properties / old_start_date / description
      Added value: +"Source course start date (ISO 8601), for date shifting"
    • addedInput schema / properties / source_course_identifier / description
      Added value: +"Course code or Canvas ID of the course to\ncopy from; must differ from the target"
    • addedInput schema / properties / target_course_identifier / description
      Added value: +"Course code or Canvas ID of the course\nthat receives the copied content"
  2. Addedv1.11.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds valuable context beyond that by explaining the preview-then-confirm safety flow and the short-lived token. It does not state what exactly is destroyed or whether the source course is left intact, keeping it below 5.

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?

Three short sentences, front-loaded with the purpose and then the two-phase mechanics. Every sentence carries actionable information with no filler.

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 destructive two-phase operation with 7 params and an output schema, the description covers the token flow, the date-shifting constraint, and preview behavior, which is enough to call correctly. Minor gaps remain around token expiry behavior and source-course impact.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds a genuinely extra constraint not captured in the schema: date shifting accepts either all four date fields or none. The token parameter semantics are already in the schema, so it doesn't go further.

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 ('full course-copy migration request') and frames the two-phase preview/confirm nature up front. An agent can tell this apart from siblings like get_content_migration_status, which is read-only status checking, 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?

Clear procedural guidance: first call to preview, second call with the token and identical arguments to execute. It does not name the alternative sibling (get_content_migration_status) or state exclusions, so it falls short of a 5.

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