Chatway Live Chat

List Conversations

list-conversations

Read-only

List accessible Chatway conversations newest first, optionally filtered by resolved status. Returns conversation metadata and a latest-message preview; use list-conversation-messages to read full message history. Use search-conversations to find a specific conversation by subject, URL, or contact instead of paging through the list.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number, starting at 1.
`status`	No	Filter conversations by resolution status.	all
`per_page`	No	Number of conversations per page, from 1 to 100.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`pagination`	No
`conversations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conversations": {
+      "items": {
+        "properties": {
+          "contact": {
+            "properties": {
+              "email": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "description": "Visitor/contact UUID.",
+                "type": "string"
+              },
+              "name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "created_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "email_subject": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ended_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_resolved": {
+            "type": "boolean"
+          },
+          "last_message": {
+            "description": "Most recent message, or null when the conversation has none.",
+            "properties": {
+              "content": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "created_at": {
+                "description": "ISO 8601 timestamp.",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "type": "string"
+              },
+              "origin": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "sender_type": {
+                "enum": [
+                  "agent",
+                  "contact",
+                  "unknown"
+                ],
+                "type": "string"
+              },
+              "type": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "origin": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "origin_url": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "resolved_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "widget_id": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "properties": {
+        "has_more": {
+          "type": "boolean"
+        },
+        "next_page": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description still adds real behavioral context: results are scoped to 'accessible' conversations, sorted newest first, and return metadata plus a latest-message preview rather than full messages.

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?

Two sentences, zero waste. The core listing behavior and ordering come first, then the two routing hints, so the most decision-relevant information is front-loaded.

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?

With an output schema present, return values need not be detailed, yet the description still characterizes the response shape. Pagination, filtering, ordering, and sibling routing are all covered for a simple read-only list tool.

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 page, per_page, and an enum status all documented in the schema, so the baseline is 3. The description restates the status filter ('optionally filtered by resolved status') but adds no syntax or 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List accessible Chatway conversations'), plus ordering ('newest first') and an optional filter. It explicitly distinguishes itself from two siblings, list-conversation-messages and search-conversations, so an agent can route without opening schemas.

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

Usage Guidelines5/5

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

Names both alternatives and the condition selecting each: use list-conversation-messages for full history, use search-conversations to find a specific conversation by subject/URL/contact rather than paging the list. That is explicit when-to-use and when-to-use-something-else guidance.

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

All Chatway Live Chat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?