Canvas MCP Server

Overview Schema Source Related Servers Discussions Admin

bulk_delete_announcements

DestructiveIdempotent

Delete multiple Canvas announcements by ID with a two-step process: preview first, then confirm using the returned token to complete permanent removal.

Instructions

Delete multiple announcements by ID. Two-step: preview first, then confirm with the token.

Permanent — Canvas may retain a recycle-bin copy depending on admin settings.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max number of announcements per call (default: 25); pass a higher value to override
`stop_on_error`	No	Stop at the first failed deletion; if False, continue with the rest (default: False). Applies to the delete phase only; the preview resolves every id regardless
`announcement_ids`	Yes	List of announcement IDs to delete
`course_identifier`	Yes	Course code or Canvas ID
`confirmation_token`	No	Token from the preview call; omit to preview

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.12.0Aug 30, 2026

addedInput schema / properties / confirmation_token

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

removedInput schema / properties / dry_run

Removed value: -{
-  "default": false,
-  "description": "Fetch titles and report what would be deleted without deleting (default: False)",
-  "type": "boolean"
-}

changedInput schema / properties / limit / description

Previous value: -"Max number of announcements to delete in one call (default: 25). Ignored when dry_run=True, so large batches can be previewed safely."New value: +"Max number of announcements per call (default: 25); pass a higher value to override"

changedInput schema / properties / stop_on_error / description

Previous value: -"Stop on first error; if False, continue with remaining (default: False)"New value: +"Stop at the first failed deletion; if False, continue with the rest (default: False). Applies to the delete phase only; the preview resolves every id regardless"

Changed1 schema field changedv1.10.0Aug 20, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null

Changed15 schema fields changedv1.8.0Aug 10, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / announcement_ids / description
```
Added value: +"List of announcement IDs to delete"
```
- removedInput schema / properties / announcement_ids / title
```
Removed value: -"Announcement Ids"
```
- 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 / dry_run / description
```
Added value: +"Fetch titles and report what would be deleted without deleting (default: False)"
```
- removedInput schema / properties / dry_run / title
```
Removed value: -"Dry Run"
```
- addedInput schema / properties / limit / description
```
Added value: +"Max number of announcements to delete in one call (default: 25). Ignored when dry_run=True, so large batches can be previewed safely."
```
- removedInput schema / properties / limit / title
```
Removed value: -"Limit"
```
- addedInput schema / properties / stop_on_error / description
```
Added value: +"Stop on first error; if False, continue with remaining (default: False)"
```
- removedInput schema / properties / stop_on_error / title
```
Removed value: -"Stop On Error"
```
- removedInput schema / title
```
Removed value: -"bulk_delete_announcementsArguments"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / title
```
Removed value: -"bulk_delete_announcementsOutput"
```
- addedOutput schema / x-fastmcp-wrap-result
```
Added value: +true
```

Changed2 schema fields changedv1.3.0May 2, 2026

addedInput schema / properties / dry_run

Added value: +{
+  "default": false,
+  "title": "Dry Run",
+  "type": "boolean"
+}

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "title": "Limit",
+  "type": "integer"
+}

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

TDQS

A4.4/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds meaningful behavioral context beyond that by warning that deletion is 'Permanent' and that a recycle-bin copy may remain depending on admin settings. It also explains the two-phase behavior and the meaning of the confirmation token, giving the agent a clear mental model of the mutation.

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?

Every sentence earns its place: the first states the operation, the second explains the workflow, and the third adds a critical permanence caveat. It is compact, front-loaded, and free of filler.

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 definition covers the core workflow and permanence caveat, and the schema fills in parameter details. Since there is no output schema, the description could have been slightly more explicit about what the preview call returns (e.g., the token), but the schema's confirmation_token description already states 'Token from the preview call; omit to preview,' so the gap is minor.

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 the schema already documents all parameters thoroughly, including the confirmation_token's role and the limit/stop_on_error behaviors. The description does not add parameter-level detail beyond the schema, so the baseline 3 is appropriate.

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?

The description opens with a specific verb-resource pair: 'Delete multiple announcements by ID.' This clearly distinguishes it from siblings like delete_announcement_with_confirmation (singular) and delete_announcements_by_criteria (criteria-based). The two-step preview/confirm flow is stated up front, making the tool's purpose unmistakable.

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?

The description gives explicit operational guidance: 'Two-step: preview first, then confirm with the token.' This tells the agent exactly how to sequence calls. It does not explicitly mention when to prefer this over sibling delete tools, but the 'by ID' scoping and bulk nature provide sufficient context for selection.

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

Deploy Server

bulk_delete_announcements

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools