Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Delete Conversation

delete_conversation
DestructiveIdempotent

Removes an Inbox conversation from your own Canvas inbox while other participants keep their copies; this action cannot be undone.

Instructions

Delete an Inbox conversation from your own inbox. Other participants keep their copy. Cannot be undone. [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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "delete_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
confirm_tokenNoThe one-time token from the preview. Only use it after the user has said yes.
conversation_idYesInbox conversation ID (numeric string). Get it from list_conversations.

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. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Inbox conversation ID (numeric string). Get it from list_conversations."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds genuinely new context: the deletion is unilateral (other participants keep their copy), it is irreversible, and it is gated behind a preview/confirm_token handshake with the user. That is exactly the behavioral detail annotations cannot express.

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?

Three short sentences plus one bracketed protocol block, all front-loaded with the scope and irreversibility warning before the mechanics. The bracket is dense but every clause carries operational information; nothing is redundant with the annotations or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world write with no output schema, the description covers impact scope, reversibility, and the full two-step invocation contract. An agent has everything needed to call it safely without guessing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema: the preview call happens first, the second call must use 'the same arguments', and confirm_token is single-use. This clarifies the coupling between confirm and confirm_token in a way the individual property descriptions do not.

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 first sentence names a specific verb (delete) and resource (Inbox conversation) and immediately scopes it: 'from your own inbox. Other participants keep their copy.' An agent can distinguish this from archive_conversation or batch_update_conversations without opening any schema.

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 bracketed section gives explicit when-and-how guidance for the two-call confirmation protocol, including the fallback for apps that can prompt the user directly. It stops short of naming the obvious non-destructive alternative (archive_conversation) for agents that only want to clear an item from view, which is the main remaining gap.

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