Skip to main content
Glama

delete_announcement

Destructive

Permanently delete a specific announcement from a Canvas course using the course identifier and announcement ID.

Instructions

Delete an announcement from a Canvas course.

    Permanent — Canvas may retain a recycle-bin copy depending on admin settings.

    Args:
        course_identifier: Course code or Canvas ID
        announcement_id: Announcement ID to delete
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
course_identifierYes
announcement_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate destructiveHint=true. The description adds useful nuance: the delete is permanent but Canvas may retain a recycle-bin copy depending on admin settings. This extra context helps the agent understand the actual behavior beyond the annotation.

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 short, front-loaded with the core purpose, and efficiently provides the permanence note and parameter explanations. Every sentence earns its place without 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 simple delete tool with only 2 parameters and an existing output schema, the description is largely complete. It covers the action, permanence, and both parameters. However, it could further clarify that this tool has no confirmation prompt (compared to its sibling) and mention any required permissions, keeping it from a perfect score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage—only titles exist. The description fills this gap with clear explanations: 'Course code or Canvas ID' for course_identifier, and 'Announcement ID to delete' for announcement_id. This adds essential meaning not present in the schema.

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 explicitly states 'Delete an announcement from a Canvas course,' which clearly identifies the verb and resource. It distinguishes from siblings like 'bulk_delete_announcements' and 'delete_announcement_with_confirmation' by implying a single, immediate delete without confirmation.

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 mentions the action is permanent and notes a recycle bin possibility, but it does not explicitly state when to use this tool versus alternatives like 'delete_announcement_with_confirmation' or 'bulk_delete_announcements'. The intent must be inferred from the name and context.

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