Skip to main content
Glama

list_scheduled_messages

Read-only

Lists the user's scheduled messages: upcoming ones and the history of past sends (sent, failed, missed, cancelled; kept 90 days). Every filter is optional and they combine. Use it to answer "what's scheduled?", to check whether scheduled messages went out (and why one failed), and to find a message's id before cancelling or changing it. A repeating message shows one row per send: the next upcoming one plus its past sends. Returns { total, returned, offset, counts_by_status, upcoming (soonest first), history (newest first) }, each message in short form { id, series_id? (only when it differs from id), status, recipient { name, phone_display, canonical_jid }, text? (the first 150 characters; text_truncated: true when cut), media?, send_at (UTC), when (readable local time and how far away), recurrence, occurrence?, until?, sent_at?, message_id?, error? }. With id, that one message comes in full: { id, series_id (shared by every send of a repeating message), status (scheduled, processing, sent, failed, missed or cancelled), recipient (contact fields (name; name_source: address_book, push_name, group_subject, business, phone or unresolved; canonical_jid: the JID to pass to send_message and read_chat_history; phone_jid and lid_jid: the chat's phone-number and LID forms, null when unknown or for groups; phone_display: the number as +).), text?, media?, send_at (UTC), send_at_local, when (readable local time and how far away), timezone, recurrence, occurrence? (0 = first send of a series), until?, sent_at?, message_id? (once sent), error? (why it failed or was missed) }. A page holds up to limit messages but stops early when they are long. If total is more than offset + returned, page with offset (the headline gives the next one) or narrow the filters. Works on the free plan too.

Input Schema

NameRequiredDescriptionDefault
idNoOptional. One scheduled message by id.
toNoOptional. Recipient: part of a name (accents and case ignored), a phone number in any format, or a JID.
textNoOptional. Only messages whose text contains this (case-insensitive).
limitNoOptional. Maximum messages to return (default 20, max 100).
offsetNoOptional. Skip this many matches, for paging (default 0).
statusNoOptional. Only these statuses, e.g. ["scheduled"] for upcoming or ["failed", "missed"] for problems.
has_mediaNoOptional. true: only messages with a file; false: only text messages.
recurringNoOptional. true: only repeating messages; false: only one-off messages.
series_idNoOptional. Every send of one repeating message.
recurrenceNoOptional. Only these repeat frequencies.
send_afterNoOptional. Only sends at or after this ISO 8601 date-time with offset.
send_beforeNoOptional. Only sends at or before this ISO 8601 date-time with offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantial behavioral context beyond them: 90-day retention, pagination that can stop early when rows are long, repeating-series row semantics, free-plan support, and detailed result-shape expectations.

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

Conciseness4/5

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

The description front-loads purpose and use cases, and its long return-shape detail is largely justified because no output schema exists. Still, the nested recipient definition and repeated status/time-format notes make it denser and harder to scan than necessary.

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

Completeness5/5

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

With 12 optional filters and no output schema, the description supplies the missing output contract, pagination guidance, retention policy, series semantics, and full-detail behavior for `id`. An agent can invoke the tool and interpret the response without further documentation.

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?

Schema description coverage is 100%, so the schema already documents all 12 filters and the baseline is 3. The description adds meaning by noting that all filters are optional and combine, that `id` switches the response to full detail, and that `limit`/`offset` interact with early stopping and `total > offset + returned` paging.

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 plus scope: listing upcoming scheduled messages and past-send history. The use-case sentence distinguishes it from creation and cancellation flows by telling the agent to use it to find a message id before cancelling or changing that message.

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 three concrete situations for use: answering what is scheduled, checking whether sends went out, and locating an id before cancelling or editing. It does not explicitly name when not to use it or point to sibling alternatives such as search_messages; the cancel/edit alternative is only implied.

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