Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create Discussion

create_discussion
Destructive

Create a discussion topic in a Canvas course by providing course ID and title. Configure message, publish status, discussion type, scheduled posting, and announcement settings.

Instructions

Create a new discussion topic in a course.

Input Schema

TableJSON 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. 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. 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))$"
  3. 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."
  4. 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"
+}
  5. First observedv1.18.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, covering the write/mutation nature of the tool. The description adds no further behavioral disclosure such as permission requirements, side effects, or the silent announcement downgrade caveat, but it does not contradict the annotations. Since the annotations lower the burden, the description is adequate though not rich in behavioral context.

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?

A single front-loaded sentence with no filler; every word contributes to stating the action and scope. It is appropriately sized for a create operation, even though it could carry more contextual detail.

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

Completeness3/5

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

For a tool with 8 parameters, no output schema, and subtle behavior such as the permission-dependent announcement downgrade, the one-sentence description is sparse. However, the input schema thoroughly documents all parameters, including the is_announcement caveat, and annotations cover the write side effect, so an agent consulting the full definition can call it correctly. The description alone would leave an agent unaware of the announcement dual-purpose.

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%, with all eight parameters documented, including a useful behavioral note on is_announcement. The tool description itself adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 ('Create'), resource ('discussion topic'), and scope ('in a course'). This clearly separates it from siblings like list_discussions, get_discussion, update_discussion, and delete_discussion. The modifier 'new' further signals it is not for editing existing discussions.

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

Usage Guidelines3/5

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

The description implies usage for creating a new discussion topic, but it offers no explicit guidance on when to prefer this tool over alternatives such as update_discussion or post_discussion_entry, nor any prerequisites or exclusions. An agent must infer the selection criteria from the verb and resource alone.

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