Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Assignment Override

create_assignment_override
Destructive

Create custom due-date or availability overrides for a Canvas assignment, targeting specific students, sections, or groups. Set unlock, due, or lock times for the chosen audience.

Instructions

Create a due-date / availability override for a specific assignment, targeting a set of students, a course section, or a group. Exactly one of student_ids, course_section_id, or group_id must be provided. At least one date field (due_at, unlock_at, lock_at) should be provided; omit a date field to leave the corresponding date unchanged for the override target. Dates must be ISO 8601 strings (e.g. "2026-09-15T23:59:00Z"). Canvas returns a 422 if a student-set override already exists for the same students on this assignment — use list_assignment_overrides to audit first. Provide student_ids as real Canvas user IDs. If CANVAS_PSEUDONYMIZE_STUDENTS is enabled, call resolve_pseudonym first to resolve pseudonyms to real user IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoHuman-readable label for this override (e.g. "Disability accommodation — Jane D").
due_atNoNew due date in ISO 8601 format. Pass null to remove the due date for this target.
lock_atNoAvailability close date in ISO 8601 format. Pass null to remove.
group_idNoID of the group to override. Mutually exclusive with student_ids and course_section_id.
course_idYesCanvas course ID
unlock_atNoAvailability open date in ISO 8601 format. Pass null to remove.
student_idsNoReal Canvas user IDs to grant the override to. Mutually exclusive with course_section_id and group_id.
assignment_idYesCanvas assignment ID
course_section_idNoID of the course section to override. Mutually exclusive with student_ids and group_id.

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. Changed6 schema fields changedv1.18.8
    • removedInput schema / properties / due_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / due_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / lock_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / lock_at / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedInput schema / properties / unlock_at / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / unlock_at / type
      Added value: +[
+  "string",
+  "null"
+]
  3. Addedv1.18.3

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description explains the behavior of omitted vs null date fields, the duplicate-override 422 failure mode, and the pseudonym-resolution prerequisite. This gives an agent actionable expectations about side effects without contradicting the annotations.

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?

Every sentence carries essential constraint or behavior information, and the most important purpose is front-loaded. Despite being longer than a one-liner, it is dense and free of 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 mutating tool with no output schema, the description thoroughly covers parameters, preconditions, and errors. The only modest gap is that it does not state what a successful response returns, but an agent can still call it correctly.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds the crucial cross-parameter invariants: exactly one selector must be provided, at least one date should be set, omitted fields remain unchanged while null removes them, and student_ids must be real Canvas user IDs. This is exactly the semantic glue the schema lacks.

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 ('Create a due-date / availability override for a specific assignment') and immediately clarifies the three target modalities. The name and description are enough to distinguish it from sibling create/update tools such as create_assignment and set_student_assignment_dates.

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?

Provides clear context and preconditions: exactly one target selector, at least one date field, ISO 8601 formatting, and a 422 pre-audit instruction via list_assignment_overrides. It does not explicitly map choice scenarios against a competing tool, but the workflow guidance is strong.

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