Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_announcement

Create a course announcement and optionally schedule its posting and auto-lock. Provide the course ID, title, and message to publish immediately or at a later time.

Instructions

Create a new announcement for a course with optional scheduling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesAnnouncement title
lock_atNoISO 8601 datetime to auto-lock the announcement
messageYesAnnouncement body content
delayed_post_atNoISO 8601 datetime to schedule posting
course_identifierYesCourse code or Canvas ID

Schema Changelog

Changes observed during successful MCP inspections.

  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. Changed15 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 announcement"
    • removedInput schema / properties / lock_at / title
      Removed value: -"Lock At"
    • addedInput schema / properties / message / description
      Added value: +"Announcement body content"
    • removedInput schema / properties / message / title
      Removed value: -"Message"
    • addedInput schema / properties / title / description
      Added value: +"Announcement title"
    • removedInput schema / properties / title / title
      Removed value: -"Title"
    • removedInput schema / title
      Removed value: -"create_announcementArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"create_announcementOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  3. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"create_announcementArguments"
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations provide idempotentHint:false and destructiveHint:false, and the description adds scheduling context (auto-lock, delayed posting) beyond them. However, it does not mention who is notified, whether existing announcements are affected, or permission requirements.

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?

Two-sentence, 19-word description that front-loads the verb 'Create' and immediately defines the resource. The optional scheduling is captured in a compact clause.

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?

With a moderate parameter count and a rich input schema covering all definitions, the description is complete enough for a creation operation. No output schema expected for a void-ish create tool; schedule semantics could be improved with a note that announcements are posted immediately if no lock/delay is set.

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?

Input schema already covers all 5 parameters (title, message, course_identifier, lock_at, delayed_post_at) with per-parameter descriptions. The description adds a little clarity (e.g., 'ISO 8601 datetime', 'Canvas ID or code'), but most semantic weight is carried by the schema. No parameter-level caveats are given.

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?

Description uses a specific verb 'create' with a clear object 'announcement' and identifies the course context and optional scheduling. It does not explicitly distinguish itself from sibling tools that also create objects (e.g., create_discussion_topic).

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 conveys a clear use case (creating an announcement) and mentions optional scheduling, but it provides no explicit when-not guidance, nor references to alternative tools such as update or delete, nor exclusions for quiz or assignment postings.

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