Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Unsubscribe Topic

unsubscribe_topic
Idempotent

Stop receiving notifications for new replies in a Canvas discussion topic while leaving the topic and your posts unchanged; reverse by subscribing again.

Instructions

Stop getting notifications for new replies in a discussion topic. Only affects you; the topic and your posts are unchanged. Reverse with subscribe_topic.

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>"
    },
    "name": "unsubscribe_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / topic_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Discussion topic ID (numeric string). Get it from list_topics."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds context the annotations cannot: the effect is scoped to the caller only, and the topic and existing posts are untouched — exactly the reassurance needed before a non-destructive write.

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

Conciseness5/5

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

Three short sentences: effect first, scope second, reversibility last. No filler, and the most important constraint is front-loaded.

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 two-parameter, non-destructive write with no output schema, the description covers the effect, the blast radius, and how to undo it. Only the return payload/confirmation behavior is unaddressed, which is minor here.

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%, with both course_id and topic_id documented including where to obtain them, so the schema already does the heavy lifting. The description adds no extra meaning about parameter relationships or formats, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Stop getting notifications for new replies in a discussion topic') and implicitly contrasts with the sibling subscribe_topic named in the final sentence. An agent can distinguish it from subscribe_topic without opening a 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 purpose makes the use case obvious, and 'Reverse with subscribe_topic' points at the opposite operation. It stops short of explicit when-to-use criteria (e.g., muting a busy topic) or prerequisites, so it is clear but not fully prescriptive.

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