Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Announcements By Criteria

delete_announcements_by_criteria
DestructiveIdempotent

Delete Canvas announcements matching title, date, or regex criteria. Preview matches first, then confirm with token to perform deletion.

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

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

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuine value on top by disclosing that deletion is permanent and that Canvas may retain a recycle-bin copy depending on admin settings. The preview-then-confirm gate is also a behavioral trait not expressible in annotations, though it omits any mention of permission requirements or what the preview returns.

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 with the destructive action and its required workflow front-loaded, followed by the permanence caveat. Nothing is repeated and nothing is padding.

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-delete with no output schema, the description covers the essential points: what qualifies for deletion, the mandatory preview/confirm handshake, and irreversibility. It leaves minor gaps around what the preview response contains and whether limit is enforced only at confirmation.

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 four parameters including the nested criteria dict and the limit safety cap are already documented in the schema. The description only echoes the confirmation_token concept via "confirm with the token" without adding format or value constraints, so the baseline 3 applies.

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?

States a specific verb and resource ("Delete announcements") plus a scoping qualifier ("matching criteria"), so the action is unambiguous. It does not, however, distinguish itself from the closely related siblings delete_announcement_with_confirmation and bulk_delete_announcements, which an agent must otherwise infer from those tools' own schemas.

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?

"Two-step: preview first, then confirm with the token" gives an explicit operational sequence that an agent must follow, which is real usage guidance rather than implied context. It stops short of naming alternatives, so it never says when to reach for bulk_delete_announcements or the single-item delete instead.

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