Canvas MCP Server

Overview Schema Source Related Servers Discussions Admin

Send Bulk Messages From List

send_bulk_messages_from_list

Send customized Canvas messages to multiple recipients using templates, with a preview-and-confirm step to review recipient count and a sample before approval.

Instructions

Send customized messages to multiple recipients using templates.

Two-step by design. Call it without a confirmation_token to get a preview (recipient count, rendered sample message) plus a token; show that preview to the educator, and only after they approve it call again with the token AND identical arguments to actually send. The token expires, is single-use, and is void if any argument changed since the preview.

Input Schema

Name	Required	Description	Default
`mode`	No	"sync" or "async"	sync
`context_code`	No	Course context
`body_template`	Yes	Body with placeholders (e.g., "Hi {name}, you have {missing_count}...")
`recipient_data`	Yes	List of dicts with recipient info and template variables
`subject_template`	Yes	Subject with placeholders (e.g., "Reminder - {missing_count} reviews")
`course_identifier`	Yes	Course code or Canvas ID
`confirmation_token`	No	Token from the preview call; omit to preview

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedv1.8.0Aug 10, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / body_template / description

Added value: +"Body with placeholders (e.g., \"Hi {name}, you have {missing_count}...\")"

removedInput schema / properties / body_template / title
```
Removed value: -"Body Template"
```

addedInput schema / properties / confirmation_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Token from the preview call; omit to preview"
+}

addedInput schema / properties / context_code / description
```
Added value: +"Course context"
```
removedInput schema / properties / context_code / title
```
Removed value: -"Context Code"
```
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 / mode / description
```
Added value: +"\"sync\" or \"async\""
```
removedInput schema / properties / mode / title
```
Removed value: -"Mode"
```

addedInput schema / properties / recipient_data / description

Added value: +"List of dicts with recipient info and template variables"

removedInput schema / properties / recipient_data / title
```
Removed value: -"Recipient Data"
```

addedInput schema / properties / subject_template / description

Added value: +"Subject with placeholders (e.g., \"Reminder - {missing_count} reviews\")"

removedInput schema / properties / subject_template / title
```
Removed value: -"Subject Template"
```

removedInput schema / title

Removed value: -"send_bulk_messages_from_listArguments"

removedOutput schema / title

Removed value: -"send_bulk_messages_from_listDictOutput"

Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / title
```
Added value: +"send_bulk_messages_from_listArguments"
```
First observedSep 27, 2025

TDQS

A4.1/5.0

Behavior5/5

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

Substantially exceeds the sparse annotations (idempotentHint=false, destructiveHint=false) by disclosing the token lifecycle: it expires, is single-use, and is void if any argument changes since the preview. It also states what the preview contains (recipient count, rendered sample), which is exactly the behavioral context needed for a mass-send operation.

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?

Front-loaded with purpose, then the two-step flow and the token constraints, in four tight sentences with no filler. Each sentence carries distinct operational information.

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?

An output schema exists, so return values need no explanation, and the confirmation flow covers the mutation risk left open by the bare annotations. Gaps remain: the async mode's behavior, recipient-volume limits or rate limits, and permission requirements are not mentioned for a 7-parameter bulk-send tool.

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%, so every parameter is already documented, and the description largely reinforces the confirmation_token contract rather than adding new per-parameter detail. It does clarify the 'identical arguments' requirement for the token, but says nothing about mode (sync vs async), context_code, or placeholder syntax beyond what the schema shows.

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?

Specific verb and resource: 'Send customized messages to multiple recipients using templates,' with the bulk/list scope implied by recipient_data. It does not explicitly name a sibling (e.g., send_conversation) to contrast against, so the agent must infer differentiation from the name and schema.

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

Usage Guidelines4/5

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

Gives a crisp operational rule: call without confirmation_token to preview, then call again with the token and identical arguments after the educator approves. It lacks guidance on when to prefer this over sibling senders like send_conversation or send_peer_review_followup_campaign, and no exclusions are stated.

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

Deploy Server