Chatway Live Chat

List Conversations

list-conversations

Read-onlyIdempotent

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

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

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 readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful return context (conversation metadata plus a latest-message preview) that tells the agent what it gets back beyond structured fields.

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?

Three tight sentences, front-loaded with the core action and ordering, followed by return shape and sibling routing. No filler.

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 annotations covering safety, a complete input schema, and an output schema to explain return values, the description supplies everything an agent needs: scope, ordering, filtering, and sibling routing.

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, per_page, and the status enum are fully documented in the schema; baseline 3 applies. The description only restates that status filtering is optional, adding little beyond the schema.

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 Chatway conversations) plus the ordering (newest first) and the optional resolved-status filter. It distinguishes itself from siblings by explicitly naming what list-conversation-messages and search-conversations are for.

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?

Gives explicit alternatives with conditions: use list-conversation-messages to read full history, use search-conversations to find a specific conversation by subject/URL/contact instead of paging. When-to-use and when-not-to-use are both covered.

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?