Skip to main content
Glama

twilio_list_messages

Lists SMS, MMS, and WhatsApp messages from a connected Twilio account, newest first, including sent and received, so you can review message history.

Instructions

(Beta) List the SMS, MMS and WhatsApp messages of a connected Twilio account, newest first, sent and receiv...

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "twilio_list_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.446

TDQS

B3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it only discloses ordering ("newest first") and message channel coverage. It says nothing about pagination, result limits, date-range behavior, or permissions, and the truncated ending ("sent and receiv...") removes whatever additional scope detail was intended.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded with the resource and channel list, which is good structure, but it is truncated and therefore not a complete sentence. The "(Beta)" prefix occupies prime real estate without explaining what the beta status implies for the caller.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter list tool with no output schema, the description covers the resource, channel types, account scope, and ordering. What is missing is volume-related context (how many messages come back, whether results are paginated) and the sentence is incomplete, so an agent cannot fully predict the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. The description does at least clarify that filtering is not expressed as inputs, reinforcing that the call returns everything in the account.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description states a specific verb and resource ("List the SMS, MMS and WhatsApp messages") and scopes it to "a connected Twilio account," which distinguishes it from the LINE/WhatsApp/Telegram reader siblings. However, it never names an alternative Twilio sibling such as twilio_get_message or twilio_list_calls, and the sentence is cut off mid-word, so the scope statement is unfinished.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of how this differs from twilio_get_message for a single message or from twilio_api_request for arbitrary queries. The only usage signal is implicit in the verb "List" and the "(Beta)" marker, which hints at instability but not at selection criteria.

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