Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Assignment

create_assignment
Destructive

Create a new assignment in a course and return the created assignment object. Each call creates another assignment — Canvas assigns a new ID every time, so check list_assignments with a search_term first to avoid duplicates.

Instructions

Create a new assignment in a course and return the created assignment object. Each call creates another assignment — Canvas assigns a new ID every time, so check list_assignments with a search_term first to avoid duplicates. Use update_assignment to change an existing assignment instead of calling this again, and delete_assignment to remove one. due_at, lock_at, and unlock_at here apply to every student; to give a different date to a subset of students, a section, or a group, use create_assignment_override instead, or set_student_assignment_dates to fan a date change for one student across many assignments. Dates are ISO 8601 strings; lock_at must be after due_at and unlock_at before due_at when both are set. Requires instructor/TA permission to manage assignments and quizzes in the course.

Input Schema

NameRequiredDescriptionDefault
nameYesAssignment name
due_atNoDue date in ISO 8601 format (e.g. 2026-05-01T23:59:00Z)
lock_atNoThe date after which the assignment locks and stops accepting submissions, in ISO 8601 format. Must be after due_at when there is one
course_idYesThe Canvas course ID
publishedNoWhether the assignment is published and visible to students
unlock_atNoThe date the assignment becomes available to students, in ISO 8601 format. Must be before due_at when there is one
descriptionNoAssignment description (HTML supported)
points_possibleNoMaximum points for this assignment
submission_typesNoAllowed submission types (e.g. ["online_upload", "online_text_entry", "none"])
assignment_group_idNoID of the assignment group to place this assignment in
omit_from_final_gradeNoWhether to leave this assignment out of the final grade calculation
grade_group_students_individuallyNoFor group assignments, whether each member is graded separately (false = one shared group grade)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.16
    • addedInput schema / properties / lock_at
      Added value: +{
+  "description": "The date after which the assignment locks and stops accepting submissions, in ISO 8601 format. Must be after due_at when there is one",
+  "type": "string"
+}
    • addedInput schema / properties / unlock_at
      Added value: +{
+  "description": "The date the assignment becomes available to students, in ISO 8601 format. Must be before due_at when there is one",
+  "type": "string"
+}
  2. Changed7 schema fields changedv1.18.15
    • addedInput schema / properties / assignment_group_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / assignment_group_id / type
      Removed value: -"number"
    • addedInput schema / properties / course_id / anyOf
      Added value: +[
+  {
+    "exclusiveMinimum": 0,
+    "maximum": 9007199254740991,
+    "type": "integer"
+  },
+  {
+    "pattern": "^[1-9][0-9]{0,18}$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / course_id / type
      Removed value: -"number"
    • addedInput schema / properties / grade_group_students_individually
      Added value: +{
+  "description": "For group assignments, whether each member is graded separately (false = one shared group grade)",
+  "type": "boolean"
+}
    • addedInput schema / properties / omit_from_final_grade
      Added value: +{
+  "description": "Whether to leave this assignment out of the final grade calculation",
+  "type": "boolean"
+}
    • addedInput schema / properties / published
      Added value: +{
+  "description": "Whether the assignment is published and visible to students",
+  "type": "boolean"
+}
  3. 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"
  4. First observedv1.18.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds behavior far beyond the annotations: non-idempotency ("each call creates another assignment — Canvas assigns a new ID every time") with a duplicate-avoidance procedure, the instructor/TA permission requirement, and cross-field validation rules (lock_at after due_at, unlock_at before due_at). The destructiveHint/openWorldHint annotations are not contradicted; the description supplies the idempotency and auth context the annotations cannot express.

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?

Front-loaded with purpose and the non-idempotency warning, and every sentence carries actionable content (dedupe check, alternatives, date constraints, permissions). It is slightly dense and long for one paragraph, which keeps it off a 5.

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

Completeness5/5

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

With 12 parameters, no output schema, and only openWorld/destructive annotations, the description covers what the structured fields cannot: idempotency, permissions, and the cross-parameter date ordering rules. Remaining fields (published, points_possible, submission_types) are already documented at 100% in the schema, so nothing an agent needs is missing.

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 the per-field baseline is 3. The description earns extra credit by explaining the semantics of the three date fields together — they apply to every student, must be ISO 8601, and carry ordering constraints — plus it routes the differential-date use case away to other tools.

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?

Opens with a specific verb+resource ("Create a new assignment in a course") and immediately names the resulting object. It explicitly distinguishes itself from update_assignment, delete_assignment, create_assignment_override, and set_student_assignment_dates, so an agent can route correctly without opening sibling schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (new assignment only), when-not-to-use (check list_assignments with search_term first; use update_assignment for changes; use create_assignment_override for per-section/group dates), plus a permission prerequisite. Alternatives and their selecting conditions are all named.

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