Skip to main content
Glama

canvas_create_conversation

Initiate a new conversation in Canvas LMS by specifying recipients, a message body, and an optional subject, enabling direct and organized communication within the platform.

Instructions

Create a new conversation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesMessage body
recipientsYesRecipient user IDs or email addresses
subjectNoMessage subject

Implementation Reference

  • src/index.ts:670-686 (registration)
    Registers the canvas_create_conversation tool in the MCP server's TOOLS array with its input schema and description.
    {
      name: "canvas_create_conversation",
      description: "Create a new conversation",
      inputSchema: {
        type: "object",
        properties: {
          recipients: { 
            type: "array", 
            items: { type: "string" },
            description: "Recipient user IDs or email addresses" 
          },
          body: { type: "string", description: "Message body" },
          subject: { type: "string", description: "Message subject" }
        },
        required: ["recipients", "body"]
      }
    },
  • Defines the input schema for validating parameters to the canvas_create_conversation tool (recipients array, body string, optional subject).
    {
      name: "canvas_create_conversation",
      description: "Create a new conversation",
      inputSchema: {
        type: "object",
        properties: {
          recipients: { 
            type: "array", 
            items: { type: "string" },
            description: "Recipient user IDs or email addresses" 
          },
          body: { type: "string", description: "Message body" },
          subject: { type: "string", description: "Message subject" }
        },
        required: ["recipients", "body"]
      }
    },
  • Executes the core logic for creating a Canvas conversation by making authenticated POST request to Canvas Conversations API endpoint.
    async createConversation(recipients: string[], body: string, subject?: string): Promise<CanvasConversation> {
      const response = await this.client.post('/conversations', {
        recipients,
        body,
        subject
      });
      return response.data;
    }
  • CanvasClient helper method invoked by MCP tool handler to perform the actual API call for creating conversations.
    async createConversation(recipients: string[], body: string, subject?: string): Promise<CanvasConversation> {
      const response = await this.client.post('/conversations', {
        recipients,
        body,
        subject
      });
      return response.data;
    }
  • TypeScript interface defining the structure of CanvasConversation response object used by the tool.
    export interface CanvasConversation {
      id: number;
      subject: string;
      workflow_state: 'read' | 'unread' | 'archived';
      last_message: string;
      last_message_at: string;
      last_authored_message: string;
      last_authored_message_at: string;
      message_count: number;
      subscribed: boolean;
      private: boolean;
      starred: boolean;
      properties: string[];
      audience: number[];
      audience_contexts: {
        [key: string]: string[];
      };
      avatar_url: string;
      participants: CanvasConversationParticipant[];
      messages?: CanvasConversationMessage[];
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create' implying a write operation, but doesn't disclose behavioral traits like permissions required, whether conversations are private or group-based, rate limits, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, response format, or error handling, leaving the agent with insufficient context to use it effectively.

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 the schema already documents all parameters (body, recipients, subject). The description adds no additional meaning beyond the schema, such as format examples or constraints (e.g., recipient types). Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the action ('Create') and resource ('new conversation'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like 'canvas_post_to_discussion' or 'canvas_list_conversations', which would require mentioning this is for direct messaging rather than course discussions.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing valid recipient IDs, or contrast with other communication tools like 'canvas_post_to_discussion' for public discussions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DMontgomery40/mcp-canvas-lms'

If you have feedback or need assistance with the MCP directory API, please join our Discord server