Skip to main content
Glama

list_messages

Read-only

List messages you've previously sent. Filter by status, recipient, notification, provider, tags, or tenant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoFilter by metadata tags
listNoFilter by list ID
tagsNoComma-delimited list of tags
eventNoFilter by event ID
cursorNoFor fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call.
statusNoFilter by status (e.g. DELIVERED, UNDELIVERABLE)
traceIdNoFilter by trace ID
archivedNoThis NARROWS, it does not widen: true returns ONLY archived messages, excluding every active one. Omit it entirely to search active messages — the default view for a normal delivery question. Setting it true is not the thorough or safe choice; it is a different, much smaller result set.
providerNoFilter by provider key (e.g. sendgrid, twilio)
messageIdNoFilter by message ID
recipientNoFilter by recipient user ID
tenant_idNoFilter by tenant ID
notificationNoFilter by notification ID
enqueued_afterNoISO 8601 timestamp; only return messages enqueued after this time

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / archived / description
      Previous value: -"Include archived messages"New value: +"This NARROWS, it does not widen: true returns ONLY archived messages, excluding every active one. Omit it entirely to search active messages — the default view for a normal delivery question. Setting it true is not the thorough or safe choice; it is a different, much smaller result set."
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor for fetching the next page"New value: +"For fetching the next page. This is an opaque token — never decode it, edit it, or rebuild it. Pass it back exactly as it appeared in the previous response's cursor field, byte for byte. Omit this entirely when you don't have one from a prior response of this exact call."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The readOnlyHint annotation already signals a safe read operation. The description adds the scope 'previously sent' but doesn't disclose behavioral details like pagination, default active-message view, or archived narrowing; those live only in the schema. It neither contradicts annotations nor adds significant behavioral context.

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?

One compact sentence states the resource and then enumerates the filter options. Every word earns its place, and the core purpose is front-loaded.

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 14-parameter listing tool, the description gives a serviceable overview but omits any mention of pagination, result scoping, or ordering. The schema fills some gaps, but the description alone leaves an agent with limited context about defaults and page traversal.

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 the schema already documents every parameter. The description restates a subset of filter dimensions without adding new meaning or clarifying usage 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.

Purpose4/5

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

The description names a specific action and resource ('List messages you've previously sent') and lists the main filter dimensions. It is clear and distinguishable from get_message/get_message_history at a glance, though it doesn't explicitly contrast itself with those siblings.

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?

The description lists filterable fields but gives no guidance on when to use this tool versus alternatives like get_message, get_message_history, or list_notifications. There is no when-to-use, when-not-to-use, or mention of sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources