Skip to main content
Glama
bruchris

Canvas LMS MCP Server

by bruchris
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Hybrid

Create Discussion

create_discussion
Destructive

Create a new discussion topic in a Canvas course by providing course ID and title. Set optional body, publishing status, schedule, type, and posting requirements.

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. Dates show when Glama detected each change.

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

TDQS

B3.3/5.0
Behavior2/5

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

The description adds no behavioral detail beyond what annotations already indicate. Although destructiveHint=true and openWorldHint=true signal mutation and potentially unexpected side effects, the description itself does not explain what changes occur, whether publishing is automatic, or how announcement requests behave. It does not contradict the annotations, but it also contributes no transparency value.

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?

The description is a single, front-loaded sentence with no filler or redundant wording. It states the core purpose efficiently, which is exactly what a concise tool description should do.

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?

The schema thoroughly documents parameters, but the overall description lacks important contextual details for a complex create operation: expected return value, publishing defaults, permission implications, and clarification that this is a write/destructive action. The annotations cover some safety context, but the description alone remains minimal for an 8-parameter tool with no output schema.

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?

All 8 parameters have rich descriptions in the input schema, including nuanced details like the is_announcement downgrade behavior and ISO 8601 datetime format. With 100% schema coverage, the description does not need to restate parameter meaning. The baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action ('Create'), a specific resource ('new discussion topic'), and scope ('in a course'). It distinguishes itself from discussion-related siblings by focusing on creation, but it does not explicitly differentiate from alternatives like post_discussion_entry or update_discussion.

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?

Usage is implied: use this when you want to create a new discussion topic. However, there is no explicit guidance about when not to use this tool or when a sibling like post_discussion_entry or update_discussion would be more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bruchris/canvas-lms-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server