Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

create_discussion_topic

Create a new discussion topic for any Canvas course by specifying the course, title, and message. Options include pinning, scheduling, locking, and requiring an initial post.

Instructions

Create a new discussion topic for a course.

IMPORTANT: Never use this tool to post or work around a failed course announcement. If create_announcement failed (e.g. insufficient permissions), report the failure to the user — do NOT post the content as a discussion instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDiscussion topic title
pinnedNoPin this discussion topic (default: False)
lock_atNoISO 8601 datetime to auto-lock the discussion
messageYesDiscussion topic body content
delayed_post_atNoISO 8601 datetime to schedule posting
course_identifierYesCourse code or Canvas ID
require_initial_postNoStudents must post before seeing others (default: False)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv1.10.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Changed19 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / delayed_post_at / description
      Added value: +"ISO 8601 datetime to schedule posting"
    • removedInput schema / properties / delayed_post_at / title
      Removed value: -"Delayed Post At"
    • addedInput schema / properties / lock_at / description
      Added value: +"ISO 8601 datetime to auto-lock the discussion"
    • removedInput schema / properties / lock_at / title
      Removed value: -"Lock At"
    • addedInput schema / properties / message / description
      Added value: +"Discussion topic body content"
    • removedInput schema / properties / message / title
      Removed value: -"Message"
    • addedInput schema / properties / pinned / description
      Added value: +"Pin this discussion topic (default: False)"
    • removedInput schema / properties / pinned / title
      Removed value: -"Pinned"
    • addedInput schema / properties / require_initial_post / description
      Added value: +"Students must post before seeing others (default: False)"
    • removedInput schema / properties / require_initial_post / title
      Removed value: -"Require Initial Post"
    • addedInput schema / properties / title / description
      Added value: +"Discussion topic title"
    • removedInput schema / properties / title / title
      Removed value: -"Title"
    • removedInput schema / title
      Removed value: -"create_discussion_topicArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"create_discussion_topicOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"create_discussion_topicArguments"
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations indicate non-idempotent and non-destructive. The description adds a caution about not using it for announcements, which helps prevent misuse, but does not detail permission requirements or side effects beyond that.

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 concise, with two sentences covering purpose and a crucial warning. No unnecessary information or verbose phrasing.

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?

The description adequately covers the tool's function and a key misuse case. Since no output schema is specified, return details are not required, and the warning adds practical completeness.

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?

The schema already provides clear descriptions for all parameters. The tool description does not add extra meaning or context beyond what the schema offers, so it stays at the baseline.

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?

Clearly states it creates a new discussion topic for a course. The description distinguishes it from announcement tools by warning against using it as a workaround, making the purpose unambiguous.

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 provides a when-not scenario: never use it to post or work around a failed course announcement. It instructs to report the failure instead, giving clear usage boundaries.

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/vishalsachdev/canvas-mcp'

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