Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Delete Bookmark

delete_bookmark
DestructiveIdempotent

Deletes one of your saved Canvas bookmarks after preview and confirmation, affecting only your account; use the bookmark ID from list_bookmarks.

Instructions

Delete one of your saved Canvas bookmarks. Only affects you. Get bookmark_id from list_bookmarks. [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": {
      "bookmark_id": "<bookmark_id>"
    },
    "name": "delete_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet to true together with confirm_token to carry out a request you already previewed.
bookmark_idYesBookmark ID (numeric string). Get it from list_bookmarks.
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
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set to true together with confirm_token to carry out a request you already previewed.",
      +  "type": "boolean"
      +}
    • 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 / bookmark_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Bookmark ID (numeric string). Get it from list_bookmarks."
  3. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered; the description adds real value by disclosing that only the caller's own bookmark is affected and by spelling out the preview/confirm_token handshake for the destructive action. It does not cover failure behavior (e.g., an unknown bookmark_id) or whether deletion is recoverable, so it falls short of a full behavioral picture.

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 personal scope are front-loaded in the first two short sentences, followed by the prerequisite and then the confirmation protocol. The bracketed confirmation block is dense but every clause (preview, show user, same arguments, confirm=true, token) is operationally necessary; only the final clause about apps asking directly feels like extra.

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, single-id mutation with no output schema and full schema coverage, this covers purpose, scoping, identifier source, and the confirmation workflow. The remaining gap is post-call behavior (error cases, confirmation that deletion succeeded), which an agent would otherwise have to discover by trial.

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 the baseline is 3, but the description adds ordering semantics the schema cannot express: the second call must repeat the same arguments with confirm=true plus the token from the first call. confirm and confirm_token are therefore explained as a paired protocol rather than two loose flags.

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?

"Delete one of your saved Canvas bookmarks" states a specific verb (delete), resource (bookmark), and scope (yours). The follow-up "Only affects you" and the pointer to list_bookmarks make it trivially distinguishable from the sibling list_bookmarks and create_bookmark.

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 says where the identifier comes from (list_bookmarks) and prescribes a two-step preview-then-confirm protocol before the destructive call, which is clear operational guidance. It stops short of naming when not to use it or what to do if the bookmark is already gone, but the usable path is 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