Twilio

Twilio List Messages

twilio_list_messages

Read-onlyIdempotent

List recent SMS/MMS messages from your Twilio account. Supports filtering by to/from number and pagination.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	No	Filter by destination phone number
`from`	No	Filter by sender phone number
`limit`	No	Max messages to return (default 20, max 100)
`_authToken`	Yes	Twilio Auth Token
`_accountSid`	Yes	Twilio Account SID

Output Schema

TableJSON Schema

Name	Required	Description
`end`	No	End index
`uri`	No	API URI for this resource
`page`	No	Current page number
`start`	No	Start index
`total`	No	Total number of messages
`messages`	No	Array of message objects
`page_size`	No	Page size
`next_page_uri`	No	URI for next page
`first_page_uri`	No	URI for first page
`previous_page_uri`	No	URI for previous page

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "end": {
+      "description": "End index",
+      "type": "integer"
+    },
+    "first_page_uri": {
+      "description": "URI for first page",
+      "type": "string"
+    },
+    "messages": {
+      "description": "Array of message objects",
+      "items": {
+        "properties": {
+          "account_sid": {
+            "description": "Account SID",
+            "type": "string"
+          },
+          "body": {
+            "description": "Message body text",
+            "type": "string"
+          },
+          "date_created": {
+            "description": "ISO 8601 creation timestamp",
+            "type": "string"
+          },
+          "date_sent": {
+            "description": "ISO 8601 sent timestamp",
+            "type": "string"
+          },
+          "date_updated": {
+            "description": "ISO 8601 update timestamp",
+            "type": "string"
+          },
+          "from": {
+            "description": "Sender phone number",
+            "type": "string"
+          },
+          "price": {
+            "description": "Message cost",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "price_unit": {
+            "description": "Currency unit",
+            "type": "string"
+          },
+          "sid": {
+            "description": "Message SID",
+            "type": "string"
+          },
+          "status": {
+            "description": "Message status",
+            "type": "string"
+          },
+          "to": {
+            "description": "Destination phone number",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_page_uri": {
+      "description": "URI for next page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "integer"
+    },
+    "page_size": {
+      "description": "Page size",
+      "type": "integer"
+    },
+    "previous_page_uri": {
+      "description": "URI for previous page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "start": {
+      "description": "Start index",
+      "type": "integer"
+    },
+    "total": {
+      "description": "Total number of messages",
+      "type": "integer"
+    },
+    "uri": {
+      "description": "API URI for this resource",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_accountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+    "_authToken": "your-twilio-auth-token",
+    "limit": 20
+  },
+  {
+    "_accountSid": "ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
+    "_authToken": "your-twilio-auth-token",
+    "from": "+15559876543",
+    "limit": 50,
+    "to": "+15551234567"
+  }
+]

First observedApr 22, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, providing a strong safety profile. The description adds that it lists recent messages and supports filtering, but doesn't elaborate on what 'recent' means or any rate limits, so it adds only minor context beyond annotations.

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?

The description is two sentences long, immediately states the core function, and includes key capabilities without extra words. It earns its place efficiently.

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?

Given that an output schema exists (documenting return values) and the tool is a simple read-only list operation, the description covers the main points: listing, filtering, pagination. Missing details like sorting or default behavior are minor given the overall clarity.

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?

The input schema has 100% description coverage for all parameters, so the baseline is 3. The description repeats that filtering by to/from and pagination exist, but adds no new meaning beyond the schema's own descriptions.

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?

The description clearly states the tool lists recent SMS/MMS messages, which is a specific verb+resource combination. It naturally distinguishes from siblings like twilio_send_sms and twilio_get_message by focusing on listing SMS/MMS.

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 description mentions filtering and pagination, implying typical use cases, but does not explicitly contrast with alternatives (e.g., twilio_get_message for single message retrieval), leaving the agent to infer when to use this tool.

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

All Twilio 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.