Skip to main content
Glama
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_announcements_by_criteria

DestructiveIdempotent

Remove Canvas announcements that match specified criteria. Preview matching items first, then confirm with the token to permanently delete them.

Instructions

Delete announcements matching criteria. 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
limitNoMax number of announcements to delete (safety limit)
criteriaYesDict with keys: title_contains, older_than (ISO), newer_than (ISO), title_regex
course_identifierYesCourse code or Canvas ID
confirmation_tokenNoToken from the preview call; omit to preview

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": true,
-  "description": "Show what would be deleted without deleting (default: True)",
-  "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 / course_identifier / description
      Added value: +"Course code or Canvas ID"
    • removedInput schema / properties / course_identifier / title
      Removed value: -"Course Identifier"
    • addedInput schema / properties / criteria / description
      Added value: +"Dict with keys: title_contains, older_than (ISO), newer_than (ISO), title_regex"
    • removedInput schema / properties / criteria / title
      Removed value: -"Criteria"
    • addedInput schema / properties / dry_run / description
      Added value: +"Show what would be deleted without deleting (default: True)"
    • removedInput schema / properties / dry_run / title
      Removed value: -"Dry Run"
    • addedInput schema / properties / limit / description
      Added value: +"Max number of announcements to delete (safety limit)"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"delete_announcements_by_criteriaArguments"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"delete_announcements_by_criteriaOutput"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"delete_announcements_by_criteriaArguments"
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already mark this as destructive and idempotent, and the description adds meaningful context: the operation is permanent, but Canvas may keep a recycle-bin copy depending on admin settings. The two-step preview/confirm flow is also a genuine behavioral disclosure beyond the annotations.

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 and front-loaded: the first sentence states what the tool does, the second explains the required workflow, and the third adds a permanence caveat. Every sentence carries useful information with no fluff.

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 tool with a two-step workflow, the description adequately conveys the preview-then-confirm process and the permanence caveat. The main gap is the lack of detail about what the preview response returns, but the schema's confirmation_token description partially covers that.

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 four parameters including the confirmation token's role. The description reinforces the token workflow but does not add much meaning beyond what the schema already provides.

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 tool deletes announcements matching criteria, with a specific verb, resource, and scope. It is distinct in intent from siblings like delete_announcement_with_confirmation, but it does not explicitly name or contrast those sibling tools, so differentiation is left largely to inference.

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 gives useful procedural guidance: preview first, then confirm with the token. However, it does not state when to choose this over bulk_delete_announcements or delete_announcement_with_confirmation, nor does it mention any exclusions or prerequisites.

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