Skip to main content
Glama

delete_announcement

DestructiveIdempotent

Delete a specific announcement from a Canvas course using its ID and course identifier. This action permanently removes the announcement, though Canvas may retain a copy in the recycle bin based on admin settings.

Instructions

Delete an announcement from a Canvas course.

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
Behavior4/5

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

Annotations already supply destructiveHint=true and idempotentHint=true. The description adds meaningful context beyond annotations by stating the deletion is permanent and that Canvas may retain a recycle-bin copy depending on admin settings. This does not contradict 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 two short sentences, front-loaded, and contains no redundant or filler content. Every sentence earns its place.

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 simple two-parameter deletion tool with destructive and idempotent annotations, the description is mostly complete. It includes permanence and recycle-bin caveats, though it could better address the existence of sibling deletion tools and expected result behavior, but this is not critical for a basic delete operation.

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?

The input schema already describes both parameters fully: announcement_id is 'Announcement ID to delete' and course_identifier is 'Course code or Canvas ID.' With 100% schema coverage, the description does not need to add parameter semantics, so a baseline of 3 is appropriate.

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 action and resource: 'Delete an announcement from a Canvas course.' It identifies a single announcement, but it does not distinguish this tool from sibling deletion tools such as delete_announcement_with_confirmation, bulk_delete_announcements, or delete_announcements_by_criteria.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus the sibling delete variants. The permanence warning implies caution but does not explain when confirmation-based, bulk, or criteria-based deletion should be preferred.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vishalsachdev/canvas-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server