Skip to main content
Glama
Sign In
vishalsachdev

Canvas MCP Server

by vishalsachdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Conversations

list_conversations
Read-only

Lists Canvas inbox conversations for the current user with scope and ID filters, returning one page plus whether more results are available.

Instructions

List conversations for the current user.

Returns one page of the inbox (Canvas's default page size). returned is how many conversations are in this response; more_available is true when Canvas reported further pages that were not fetched.

Input Schema

NameRequiredDescriptionDefault
scopeNo"unread", "starred", "sent", "archived", or "all"unread
filter_idsNoConversation IDs to filter by
filter_modeNo"and" or "or" for filter_idsand
include_all_idsNoInclude all participant IDs
include_participantsNoInclude participant info

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv1.8.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / filter_ids / description
      Added value: +"Conversation IDs to filter by"
    • removedInput schema / properties / filter_ids / title
      Removed value: -"Filter Ids"
    • addedInput schema / properties / filter_mode / description
      Added value: +"\"and\" or \"or\" for filter_ids"
    • removedInput schema / properties / filter_mode / title
      Removed value: -"Filter Mode"
    • addedInput schema / properties / include_all_ids / description
      Added value: +"Include all participant IDs"
    • removedInput schema / properties / include_all_ids / title
      Removed value: -"Include All Ids"
    • addedInput schema / properties / include_participants / description
      Added value: +"Include participant info"
    • removedInput schema / properties / include_participants / title
      Removed value: -"Include Participants"
    • addedInput schema / properties / scope / description
      Added value: +"\"unread\", \"starred\", \"sent\", \"archived\", or \"all\""
    • removedInput schema / properties / scope / title
      Removed value: -"Scope"
    • removedInput schema / title
      Removed value: -"list_conversationsArguments"
    • removedOutput schema / title
      Removed value: -"list_conversationsDictOutput"
  2. Changed1 schema field changedv1.0.0
    • addedInput schema / title
      Added value: +"list_conversationsArguments"
  3. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds genuinely new behavioral context: results are a single page at Canvas's default page size, and more_available signals unfetched pages. That pagination contract is the key operational detail an agent needs and is not derivable from the annotations.

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?

Three short sentences with the core action front-loaded and pagination details following. No filler, though the explanation of `returned` is mildly redundant with the output schema.

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?

A read-only listing tool with full schema coverage and an output schema; the description covers pagination behavior, which is the main thing not carried by structured fields. Nothing critical is missing, though sibling routing guidance would complete it.

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 description coverage is 100%, with every parameter (scope, filter_ids, filter_mode, include_all_ids, include_participants) documented inline, so the baseline is 3. The description adds no further meaning about scope values or filter semantics beyond what the schema already provides.

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?

States a specific verb and resource ("List conversations") with the scope qualifier "for the current user", so an agent knows this is a paginated inbox listing. It does not distinguish itself from nearby siblings such as get_conversation_details or get_unread_count, but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to use this tool versus the alternatives in the sibling set (get_conversation_details for a single thread, get_unread_count for a count, search tools for filtering). Usage is only implied by the word "List"; no exclusions or prerequisites are given.

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