Skip to main content
Glama
vivernet

Chatwoot MCP Server

by vivernet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Chatwoot Conversation Details

chatwoot_get_conversation
Read-onlyIdempotent

Retrieve complete details for a single Chatwoot conversation, including contact information, assignee, labels, and custom attributes.

Instructions

Get detailed information about a specific Chatwoot conversation.

This tool retrieves full details for a single conversation including contact info, assignee, labels, and custom attributes.

Args:

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

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

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

Returns: Full conversation details including:

  • Status, inbox, and metadata

  • Complete contact information

  • Assignee details

  • Labels and custom attributes

  • Message statistics

Examples:

  • Get conversation details: { 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.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and openWorld, so the safety profile is handled. The description adds genuine context beyond that by enumerating what the response contains (contact info, assignee, labels, custom attributes, message statistics), which helps the agent decide whether one call suffices.

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?

Front-loaded purpose sentence followed by sharply organized sections. There is mild redundancy in restating Args and Returns that the schema and annotations partly cover, but nothing is padded with filler.

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?

With no output schema, describing the returned fields is the right use of space, and the description does that. It stops short of covering error behavior or what happens for a nonexistent conversation ID, but otherwise an agent has what it needs.

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, including the response_format enum. The Args block restates them without adding format, constraint, or failure-mode detail, so 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 ('Get detailed information about a specific Chatwoot conversation') and implicitly contrasts with chatwoot_list_conversations by scoping to a single conversation with full details. An agent can select it without ambiguity.

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 phrase 'a specific conversation' implies when to use it versus the list sibling, but there is no explicit when-to-use/when-not guidance, no prerequisites, and no named alternatives such as chatwoot_list_messages for message data.

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