Chatway Live Chat

List Conversation Messages

list-conversation-messages

Read-onlyIdempotent

List messages from one accessible Chatway conversation, newest first. Supports pagination and optional inclusion of system messages and private/internal message types. Read the history before summarizing or replying; page back to older messages with before_sort_number.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of messages to return, from 1 to 100.
`conversation_id`	Yes	The UUID of the conversation whose messages should be retrieved.
`before_sort_number`	No	Return messages older than this sort number. Use next_before_sort_number from the previous response.
`include_system_messages`	No	Whether to include system-generated messages.
`include_internal_messages`	No	Whether to include internal notes, reminders, and other non-chat message types.

Output Schema

Name	Required	Description	Default
`messages`	No
`pagination`	No
`conversation_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "conversation_id": {
+      "type": "string"
+    },
+    "messages": {
+      "items": {
+        "properties": {
+          "content": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "conversation_id": {
+            "type": "string"
+          },
+          "created_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "edited_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "id": {
+            "type": "string"
+          },
+          "is_system_message": {
+            "type": "boolean"
+          },
+          "origin": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "parent_id": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "sender": {
+            "properties": {
+              "email": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "id": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "name": {
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "type": {
+                "enum": [
+                  "agent",
+                  "ai_assistant",
+                  "contact",
+                  "system",
+                  "unknown"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "sort_number": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "type": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "updated_at": {
+            "description": "ISO 8601 timestamp.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "urls": {
+            "type": [
+              "array",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "pagination": {
+      "properties": {
+        "has_more": {
+          "type": "boolean"
+        },
+        "limit": {
+          "type": "integer"
+        },
+        "next_before_sort_number": {
+          "description": "Pass as before_sort_number to load older messages.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds useful traits beyond that: fixed ordering, pagination support, and that system/internal messages are excluded unless opted in.

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 sentences, each carrying distinct information: scope and ordering first, capability second, operational guidance third. No 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?

Covers purpose, ordering, pagination and filtering, and an output schema plus read-only annotations handle return shape and safety. Only minor gaps remain, such as default page size, which the schema already supplies.

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 every parameter is already documented in the schema, including the `next_before_sort_number` paging hint. The description's mention of pagination and optional message types largely restates that, adding little new meaning.

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 messages'), scopes it to 'one accessible Chatway conversation', and adds the ordering ('newest first'). That is enough to separate it from get-conversation and list-conversations without opening a schema.

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

Usage Guidelines4/5

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

Gives an explicit usage cue ('Read the history before summarizing or replying') and tells the agent how to page backwards with `before_sort_number`. It does not name a sibling alternative or state exclusions, so it falls short of a 5.

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?