Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Delete My File

delete_my_file
DestructiveIdempotent

Deletes a file from personal Canvas storage by file ID; the irreversible action requires a preview and confirm_token before removal.

Instructions

Delete a file from your personal Canvas storage. Cannot be undone. Get file_id from list_my_files. [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": {
      "file_id": "<file_id>"
    },
    "name": "delete_my_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
file_idYesFile ID (numeric string). Get it from list_course_files, list_my_files or list_group_files.
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. Changed1 schema field changedv1.1.3
    • changedInput schema / properties / file_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"File ID (numeric string). Get it from list_course_files, list_my_files or list_group_files."
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the irreversibility warning largely restates structured data. The genuinely additive context is the mandatory confirmation protocol and the fact that the first call yields a preview plus one-time confirm_token — behavior the annotations do not 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?

Purpose, irreversibility, and ID source come first, followed by the bracketed confirmation protocol — a sensible front-loaded order. The bracketed block is dense and somewhat long, but each clause (preview, show user, second call, arguments) carries operational weight.

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 mutation with no output schema, the description covers the critical gaps: irreversibility, ID provenance, and the two-step safety protocol including what the preview returns. It omits secondary details such as permission requirements or what happens to quota/space after deletion, which are minor here.

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 all three parameters are documented in the schema already. The description's contribution is sequencing semantics: confirm and confirm_token are only valid on the second call after user approval, which clarifies the interaction between parameters beyond their individual definitions.

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 opens with a specific verb and resource scoped to 'your personal Canvas storage', which cleanly separates it from delete_bookmark, delete_my_entry, and delete_conversation. It also states the ID source, so an agent knows exactly which object this destroys.

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?

It gives concrete routing to list_my_files for the file_id and, more importantly, a full when/how procedure via the two-phase confirmation flow (preview call, user approval, second call with confirm=true and the token). It does not explicitly contrast with other delete tools, but the resource scope makes the choice unambiguous.

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