Skip to main content
Glama

List Conversations

list_conversations
Read-onlyIdempotent

List Canvas Inbox conversations newest first to review subjects, participants, message previews and unread status; use for inbox overview before opening a full thread.

Instructions

List your Canvas Inbox conversations, newest first, with subject, participants, last message preview and unread state. Read-only. Use get_conversation for the full thread.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWhich page of results to show, starting at 1. Use it when a result says there are more.
limitNoMaximum number of items to return (one page of results). Smaller is faster.
scopeNoWhich mailbox: "inbox" (default), "unread", "starred", "archived" or "sent".
filterNoOptional filter by course or user, e.g. "course_12345".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of items to return. Smaller is faster."New value: +"Maximum number of items to return (one page of results). Smaller is faster."
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Which page of results to show, starting at 1. Use it when a result says there are more.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
  2. Changed3 schema fields changedv1.0.2
    • changedInput schema / properties / filter / description
      Previous value: -"e.g. course_123"New value: +"Optional filter by course or user, e.g. \"course_12345\"."
    • changedInput schema / properties / limit / description
      Previous value: -"Max items to return"New value: +"Maximum number of items to return. Smaller is faster."
    • addedInput schema / properties / scope / description
      Added value: +"Which mailbox: \"inbox\" (default), \"unread\", \"starred\", \"archived\" or \"sent\"."
  3. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered and the redundant "Read-only" sentence adds little. The description does add real behavior beyond the annotations: ordering (newest first) and the exact shape of each list item, which tells the agent it receives a summary rather than full message bodies.

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, front-loaded with purpose then the return contents then the sibling redirect. The "Read-only" sentence is the only filler, since annotations already state it, but the cost is minimal.

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

Completeness5/5

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

For a no-required-parameter paginated list tool with no output schema, the description supplies the missing return-value information (fields per item, ordering), the safety profile nuance, and the alternative tool for the deeper read. Nothing an agent needs to invoke it correctly is absent.

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%, so page, limit, scope and filter are all already documented with examples. The description adds only the sort order, which is not a parameter at all; it contributes no per-parameter meaning beyond the schema, 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?

Uses a specific verb and resource ("List your Canvas Inbox conversations") and enumerates what each item contains: subject, participants, last message preview, unread state. It also names the sibling get_conversation as the tool for the full thread, so an agent can distinguish the two 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 clause "Use get_conversation for the full thread" gives an explicit alternative and the condition that selects it, which is the most important routing decision for this tool. It stops short of explaining when to pick the unread/starred/archived scopes versus related tools like get_all_unread or get_unread_conversation_count.

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