Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Bulk Delete Announcements

bulk_delete_announcements
DestructiveIdempotent

Delete multiple Canvas announcements by ID using a two-step flow: preview the affected items first, then confirm with the returned token.

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

NameRequiredDescriptionDefault
limitNoMax number of announcements per call (default: 25); pass a higher value to override
stop_on_errorNoStop 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_idsYesList of announcement IDs to delete
course_identifierYesCourse code or Canvas ID
confirmation_tokenNoToken from the preview call; omit to preview

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.12.0
    • 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"
  2. 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
  3. Changed15 schema fields changedv1.8.0
    • 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
  4. Changed2 schema fields changedv1.3.0
    • 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"
+}
  5. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"bulk_delete_announcementsArguments"
  6. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds valuable context that deletions are 'Permanent' with a caveat about Canvas recycle-bin retention. It stops short of describing error behavior or permission requirements, but the added permanence nuance is meaningful beyond structured data.

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 short sentences, front-loaded with the core action and workflow. Every sentence earns its place: the first defines the operation and two-step process, the second clarifies permanence and a key caveat.

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?

For a destructive bulk operation with full schema coverage and annotations, the description covers the critical workflow and permanence caveat. It omits some finer points like error handling or output shape, but those are either covered by schema parameters (e.g., stop_on_error) or unnecessary for a delete 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?

Schema description coverage is 100%, so all five parameters are fully documented in the input schema. The description reiterates 'by ID' and 'confirm with the token' but adds no syntax, format, or edge-case details beyond what the schema already provides.

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 states a specific verb ('Delete'), resource ('announcements'), and scope ('multiple ... by ID'), immediately distinguishing it from single-delete or criteria-based siblings. An agent can tell this is for bulk deletion by explicit IDs without opening the 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?

It clearly outlines the two-step workflow ('preview first, then confirm with the token'), which is essential for correct invocation. However, it does not explicitly name when to use this tool versus siblings like delete_announcement_with_confirmation or delete_announcements_by_criteria, leaving some inference to the agent.

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