Skip to main content
Glama

List Messages (Telnyx)

phone.telnyx.list
Read-onlyIdempotent

Retrieve recent Telnyx messages with filters for direction, date, and limit. Returns message ID, sender, receiver, text, status, timestamp, and cost.

Instructions

List recent Telnyx messages with optional filters: direction (inbound/outbound), date_from (ISO 8601), and pagination limit (max 100). Returns array of {message_id, from, to, text, status, created_at, cost} (Telnyx)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax number of messages to return per page (default 25, max 100).
directionNoFilter by message direction: "outbound" (sent by us) or "inbound" (received).
date_fromNoISO 8601 date — return messages created on or after this date (e.g. "2026-04-26").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, making the safety profile clear. The description adds return format details but no additional behavioral traits (e.g., rate limits, ordering). With annotations, the bar is met but not exceeded.

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, front-loaded with purpose and filters, then return format. No wasted words. Every sentence earns its place.

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, filters, and output structure. Lacks pagination details (e.g., default limit, next page token) and ordering, but for a simple list tool with output schema in description, it is fairly complete.

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 coverage is 100% with each parameter described. The tool description repeats filter names and types but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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?

Clearly states the tool lists Telnyx messages with optional filters, distinguishing it from sibling tools like phone.telnyx.sms_na (send SMS) or phone.telnyx.balance (check balance). The verb 'list' and resource 'Telnyx messages' are specific.

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 implies usage for retrieving message history with filters, but lacks explicit guidance on when to use this vs alternatives (e.g., not for sending messages) and no exclusions. The context of siblings is not leveraged.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/whiteknightonhorse/APIbase'

If you have feedback or need assistance with the MCP directory API, please join our Discord server