Skip to main content
Glama
vivernet

Chatwoot MCP Server

by vivernet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Messages in Conversation

chatwoot_list_messages
Read-onlyIdempotent

Retrieve all messages from a specific Chatwoot conversation by account and conversation ID, including content, sender, timestamps, attachments, and private notes.

Instructions

List all messages in a Chatwoot conversation.

This tool retrieves all messages from a specific conversation, including message content, sender information, timestamps, and attachments.

Args:

  • account_id (number): The numeric ID of the Chatwoot account (required)

  • conversation_id (number): The ID of the conversation (required)

  • response_format (string): Output format - "markdown" or "json" (default: "markdown")

Returns: List of messages with:

  • Message ID and content

  • Message type (incoming/outgoing)

  • Sender information (name, type)

  • Timestamp

  • Attachment information

  • Private flag (for internal notes)

Examples:

  • List all messages: { account_id: 1, conversation_id: 123 }

Input Schema

NameRequiredDescriptionDefault
account_idYesThe numeric ID of the account
conversation_idYesThe ID of the conversation
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context by listing the returned message fields, including sender information, attachments, timestamps, and private-note flags, though it does not discuss pagination or rate limits.

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

Conciseness3/5

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

The description is well-organized with Args, Returns, and Examples sections, and the main purpose is front-loaded. However, the Args section largely duplicates the fully documented schema, and the Returns section is somewhat verbose for a simple read operation.

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 simple read-only tool with complete schema coverage and annotations, the description gives sufficient context about inputs and returned fields. The absence of pagination or volume-limit details is a minor gap, but it is otherwise complete enough for an agent to invoke correctly.

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 all three parameters are already documented in the schema. The description repeats the arguments and clarifies the response_format options, but adds little meaning beyond what the schema 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?

The description uses a specific verb and resource: "List all messages in a Chatwoot conversation." It clearly distinguishes this from message creation and conversation-level retrieval by focusing on messages within a specific conversation, though it does not explicitly name sibling alternatives.

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

Usage Guidelines3/5

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

The usage context is implied by "retrieves all messages from a specific conversation" and an example is provided. However, there is no explicit guidance on when to use this instead of sibling tools such as chatwoot_get_conversation or chatwoot_create_message, and no exclusions are stated.

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