Skip to main content
Glama
Canvas LMS MCP – Remote Edition

Canvas LMS MCP – Remote Edition

Unstar Conversation

unstar_conversation
Idempotent

Removes the star from a Canvas Inbox conversation for your account only, leaving the conversation unchanged; use star_conversation to reverse it.

Instructions

Remove the star from an Inbox conversation. Only affects you; the conversation itself is unchanged. Reverse with star_conversation.

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": "unstar_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesInbox conversation ID (numeric string). Get it from list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  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 idempotent and non-destructive, but the description adds real value by scoping the effect to the caller only ('Only affects you; the conversation itself is unchanged'), which is the key risk question for a per-user flag toggle. Minor gap: no mention of what happens for already-unstarred conversations.

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, each carrying distinct information (action, scope of effect, inverse operation) with the core action front-loaded. Nothing is redundant.

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 one-parameter flag toggle with a fully documented schema and informative annotations, the description covers action, blast radius, and the inverse. Only the already-unstarred edge case is unaddressed, which is minor given the idempotent hint.

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% and the single parameter's schema description already documents format and where to obtain the ID (list_conversations). The description adds no parameter-level meaning, so the baseline 3 applies.

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 ('Remove the star from an Inbox conversation') and immediately distinguishes itself from the inverse sibling star_conversation. An agent can select it over star_conversation/delete_conversation 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 'Reverse with star_conversation' clause gives explicit routing to the alternative and implies when each is appropriate. It does not spell out when-not-to-use (e.g. for another user's view), so it stops short of a full 5.

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