Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Batch Update Conversations

batch_update_conversations
Destructive

Apply one action—mark read/unread, star/unstar, archive, or delete—to multiple Canvas Inbox conversations at once. Preview and confirm before changes.

Instructions

Apply one action (mark read or unread, star, unstar, archive or delete) to many Inbox conversations at once. Only affects your own inbox. [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_ids": "<conversation_ids>",
      "event": "<event>"
    },
    "name": "batch_update_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventYesAction to apply to every listed conversation. "destroy" deletes them from your inbox for good.
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_idsYesInbox conversation IDs (numeric strings) 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. Changed2 schema fields changedv1.1.3
    • addedInput schema / properties / conversation_ids / description
      Added value: +"Inbox conversation IDs (numeric strings) from list_conversations."
    • addedInput schema / properties / event / description
      Added value: +"Action to apply to every listed conversation. \"destroy\" deletes them from your inbox for good."
  3. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, so the risk profile is supplied by structured data. The description's real addition is the two-phase preview/confirm_token flow and the "only affects your own inbox" scoping, which is meaningful context. It does not add much beyond that on rate limits, partial-failure behavior, or what the preview actually contains.

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?

Two tight sentences with the action list front-loaded and the confirmation procedure second. The bracketed NEEDS CONFIRMATION block is slightly awkward in tone but carries real operational content, so nothing is genuinely wasteful.

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

Completeness3/5

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

For a destructive bulk mutation with no output schema, the definition covers the confirmation flow but leaves blanks: what the preview returns, whether a batch can partially succeed, and what a successful response looks like. It is adequate to call the tool safely but not fully complete.

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 the enum, conversation_ids source, and confirm/confirm_token semantics are already documented in the schema. The description adds one useful constraint implied by "with the same arguments" — the retry must be argument-identical — but otherwise restates the schema's story.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ("Apply one action") and resource ("many Inbox conversations"), and enumerates the allowed actions (read/unread, star, unstar, archive, delete). The phrase "to many ... at once" implicitly separates it from the single-conversation siblings, but it never names them, so the differentiation is inferred rather than stated.

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?

Strong explicit protocol: call once for a preview, show it to the user, and call again with the same arguments plus confirm=true and the token only after approval, including the caveat for apps that can ask the user directly. The gap is that it never says when to use bulk versus per-conversation tools like mark_conversation_read or archive_conversation.

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