Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_announcement_with_confirmation

DestructiveIdempotent

Delete a Canvas course announcement in two steps: preview to receive a confirmation token, then confirm the deletion with that token.

Instructions

Delete an announcement. 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
NameRequiredDescriptionDefault
announcement_idYesAnnouncement ID to delete
course_identifierYesCourse code or Canvas ID
confirmation_tokenNoToken from the preview call; omit to preview
require_title_matchNoOnly delete if title matches this string exactly

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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": "Verify but don't actually delete (default: False)",
-  "type": "boolean"
-}
  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. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / announcement_id / description
      Added value: +"Announcement ID to delete"
    • removedInput schema / properties / announcement_id / title
      Removed value: -"Announcement Id"
    • 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: +"Verify but don't actually delete (default: False)"
    • removedInput schema / properties / dry_run / title
      Removed value: -"Dry Run"
    • addedInput schema / properties / require_title_match / description
      Added value: +"Only delete if title matches this string exactly"
    • removedInput schema / properties / require_title_match / title
      Removed value: -"Require Title Match"
    • removedInput schema / title
      Removed value: -"delete_announcement_with_confirmationArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"delete_announcement_with_confirmationOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"delete_announcement_with_confirmationArguments"
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint, destructiveHint), the description discloses meaningful behavioral details: the two-step preview/confirm process and the permanence caveat with recycle-bin behavior depending on admin settings. This adds real context for an agent deciding whether and how to invoke it safely.

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 compact, front-loads the core action, and packs essential process and permanence information into two short sentences. Every sentence earns its place with no redundancy.

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 two-step operation, the description covers the workflow and permanence clearly, and the schema covers parameters in full. It does not explicitly explain what the preview response contains or how to distinguish this from bulk/criteria-based deletion tools, but the provided information is largely sufficient for correct invocation.

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, including the confirmation token and optional title match. The description reinforces the preview/confirm flow but does not add meaning beyond what the schema provides, so it stays at the baseline of 3.

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?

The description clearly states the operation: "Delete an announcement" with a specific verb and resource, and adds the two-step confirmation feature. However, it does not explicitly distinguish itself from sibling tools like bulk_delete_announcements or delete_announcements_by_criteria, so it lacks direct sibling differentiation.

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 clear context on how to use the tool: preview first, then confirm with a token. This implies single-announcement deletion with a safety confirmation flow, which is useful guidance. It does not explicitly state when not to use it or list alternative deletion tools, so it stops short of full usage differentiation.

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