Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Delete My Entry

delete_my_entry
DestructiveIdempotent

Delete one of your own Canvas discussion entries when the course allows it, with a preview and confirmation step before the removal.

Instructions

Delete one of your own discussion entries, if the course allows it. Classmates see that an entry was removed. [NEEDS CONFIRMATION: call it once for a preview and a confirm_token, show the preview to the user, and only if they say yes call it again with the same arguments, confirm=true and that confirm_token. Apps that can ask the user directly show a confirmation instead.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course_id": "<course_id>",
      "topic_id": "<topic_id>",
      "entry_id": "<entry_id>"
    },
    "name": "delete_my_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
entry_idYesDiscussion entry ID (numeric string). Get it from get_full_topic_view or list_entries.
topic_idYesDiscussion topic ID (numeric string). Get it from list_topics.
course_idYesCanvas course ID, a numeric string such as "12345". Get it from list_courses.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.4.0
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true to actually execute. Omit or set false to get a dry-run preview first."New value: +"Set to true together with confirm_token to carry out a request you already previewed."
    • addedInput schema / properties / confirm_token
      Added value: +{
      +  "description": "The one-time token from the preview. Only use it after the user has said yes.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changedv1.1.3
    • changedInput schema / properties / course_id / description
      Previous value: -"Canvas course ID"New value: +"Canvas course ID, a numeric string such as \"12345\". Get it from list_courses."
    • changedInput schema / properties / entry_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion entry ID (numeric string). Get it from get_full_topic_view or list_entries."
    • changedInput schema / properties / topic_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion topic ID (numeric string). Get it from list_topics."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds what those annotations cannot: that the deletion is permission-gated by the course, that classmates will see an entry was removed (i.e., a placeholder remains rather than a silent erasure), and the two-phase preview/confirm protocol with token reuse requirements. That is material behavior beyond the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the side effect on classmates are front-loaded in two short sentences, and the confirmation protocol follows. The bracketed "[NEEDS CONFIRMATION: ...]" wrapper is awkward tooling-style formatting and could be prose, but the content inside earns its length.

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, open-world mutation with no output schema, the description covers the safety-critical pieces: permission gating, the visible consequence for other users, and the exact confirmation handshake. It stops short of describing failure modes (e.g., what happens if the course forbids deletion, or if the token expires), which an agent would have to discover by trial.

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 coverage is 100%, so course_id, topic_id, entry_id, confirm, and confirm_token are each documented in the schema, including where to obtain the IDs. The description explains how confirm and confirm_token combine into a workflow, but that is largely duplicated from the token field description rather than adding new per-parameter meaning.

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 gives a specific verb and resource ("Delete one of your own discussion entries") and scopes ownership with "your own", which cleanly separates it from edit_my_entry, delete_bookmark, and delete_conversation in the sibling list. The conditional "if the course allows it" further narrows the operation.

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 usage flow is spelled out in unusual detail: call once for a preview, show the preview, then call again with confirm=true and the token only after the user agrees. The gap is that no sibling alternative is named for the case where the user wants to retract content another way, but the when-and-how is otherwise explicit.

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