Skip to main content
Glama
Sign In
Canvas LMS MCP Server

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Discussion

create_discussion
Destructive

Create a new discussion topic in a course, and return the created topic (id, title, message, discussion_type, published, is_announcement, posted_at).

Instructions

Create a new discussion topic in a course, and return the created topic (id, title, message, discussion_type, published, is_announcement, posted_at). Not idempotent: each call creates another topic — Canvas does not deduplicate by title, so check list_discussions first to avoid creating a duplicate. Setting is_announcement: true asks Canvas to create an announcement, but Canvas silently creates a plain discussion topic instead (HTTP 200, no error) if the caller lacks announcement-create permission in the course — this tool then throws instead of reporting success, naming the topic ID so you can check it with list_discussions or get_discussion. Use update_discussion to change an existing topic afterward, delete_discussion to remove one, and post_discussion_entry to reply to a topic instead of creating a new one. Requires instructor/TA permission to manage discussions in the course.

Input Schema

NameRequiredDescriptionDefault
titleYesTitle of the discussion topic
messageNoBody text of the discussion (supports HTML)
course_idYesThe Canvas course ID
publishedNoWhether the topic is published
delayed_post_atNoISO 8601 datetime to schedule the topic for future posting
discussion_typeNoDiscussion type: side_comment (flat) or threaded
is_announcementNoWhen true, requests an announcement instead of a discussion topic. Canvas silently downgrades this to a plain discussion topic (no error) if the caller lacks announcement permission in the course — check the response's own `is_announcement` field rather than assuming the request was honored.
require_initial_postNoRequire students to post before seeing replies

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.15
    • 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"
  2. 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"
  3. Changed1 schema field changedv1.18.8
    • changedInput schema / properties / delayed_post_at / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
  4. Changed1 schema field changedv1.18.4
    • changedInput schema / properties / is_announcement / description
      Previous value: -"When true, creates an announcement instead of a discussion topic"New value: +"When true, requests an announcement instead of a discussion topic. Canvas silently downgrades this to a plain discussion topic (no error) if the caller lacks announcement permission in the course — check the response's own `is_announcement` field rather than assuming the request was honored."
  5. Changed2 schema fields changedv1.18.3
    • addedInput schema / properties / delayed_post_at
      Added value: +{
+  "description": "ISO 8601 datetime to schedule the topic for future posting",
+  "format": "date-time",
+  "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
+  "type": "string"
+}
    • addedInput schema / properties / is_announcement
      Added value: +{
+  "description": "When true, creates an announcement instead of a discussion topic",
+  "type": "boolean"
+}
  6. First observedv1.18.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag openWorldHint and destructiveHint; the description supplies far more: non-idempotency with no server-side dedupe by title, the silent downgrade of is_announcement to a plain topic with HTTP 200, and the tool's own throw-with-topic-ID failure behavior so the caller can verify via list_discussions/get_discussion. These are exactly the non-obvious failure modes an agent needs before calling a mutation.

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 return shape, then caveats, then sibling routing — good ordering with no filler. The is_announcement sentence is long and partially restates the schema field description, so it is dense rather than perfectly tight.

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?

No output schema exists, so the description compensates by naming returned fields. Combined with permission requirements, non-idempotency, and the silent-downgrade failure path, an agent has everything needed to invoke this correctly and interpret the outcome.

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 still adds meaning by tying the title parameter to Canvas's lack of dedupe and by reinforcing that is_announcement's response field must be checked rather than the request assumed honored. It does not, however, cover delayed_post_at, published, or require_initial_post beyond what the schema says.

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 new discussion topic in a course') and enumerates the returned fields (id, title, message, discussion_type, published, is_announcement, posted_at), which distinguishes it from sibling reads like get_discussion and list_discussions. An agent can pick it out of a large sibling list 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 Guidelines5/5

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

Explicitly routes to alternatives: check list_discussions first to avoid duplicates, use update_discussion to modify, delete_discussion to remove, post_discussion_entry to reply. It also states the prerequisite (instructor/TA permission to manage discussions).

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