Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Content Migration

create_content_migration
Destructive

Start a content migration for course copy or import (Common Cartridge, zip, QTI, Moodle). Returns a migration ID and progress URL to track completion.

Instructions

Start a content migration (course copy, Common Cartridge import, zip import, QTI conversion, or Moodle conversion). Migrations are asynchronous — this tool returns immediately with a migration ID and progress_url. Poll get_content_migration or progress_url to track completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
settingsNoMigration-type-specific settings. For course_copy_importer, pass { source_course_id: <id> }.
course_idYesThe destination Canvas course ID
migration_typeYesThe type of migration to run
selective_importNoIf true, migration enters "waiting_for_select" state so you can choose which content to import via get_migration_selective_data.
date_shift_optionsNoOptions for shifting dates during the migration (e.g. { shift_dates: true, old_start_date: "...", new_start_date: "..." }).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.18.11
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.18.4

TDQS

A4/5.0
Behavior3/5

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

Usefully discloses the non-blocking behavior and immediate return of an ID and progress_url. With openWorldHint and destructiveHint annotations, the description does not add detail about what gets modified or overwritten in the destination course, whether rollback is possible, or what failure states look like. It still adds value over the annotations by explaining the asynchronous nature.

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 compact sentences carry the full purpose, the supported type list, and the polling advice. Information is front-loaded with no filler or redundant restatement of the schema.

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?

Coverage is solid for a 5-parameter, nested-object create tool with no output schema: it says what it returns and how to monitor completion. It does not describe the destructive side effects or exception/import issue conditions, but given the annotations and rich schema, it is mostly complete.

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 all five parameters. The description adds little new meaning about settings, selective_import, or date_shift_options, but it does clarify the return concept. Baseline 3 is appropriate.

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 action ('start a content migration'), lists all supported migration types, and frames the asynchronous result (migration ID and progress_url). This clearly separates it from the get/list migration tools and from content export tools.

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?

Explains the async contract and directs follow-up polling to get_content_migration or progress_url, which is helpful usage context. It doesn't explicitly state when not to use it or mention non-migration alternatives, but the supported types plus async guidance are enough for selection.

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