Skip to main content
Glama

Schedule Text Message

schedule_message
Destructive

Schedule a message to be sent at a specific time in the future via Mobile Text Alerts API. Use this tool when you need to send a message at a later date/time rather than immediately. The message goes out from the account's default number (the one it last sent from) unless from names another; the response's sentFrom says which was used.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "message": "<message>",
      "scheduledDate": "<scheduledDate>"
    },
    "name": "schedule_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number (can be formatted as +1234567890, 234-567-8900, (234) 567-8900, etc.)
fromNoSending phone number. Omit to use the account's default (the number it last sent from). Use list_sending_numbers to see options.
messageYesMessage content to send
scheduledDateYesUTC date/time when the message should be sent. IMPORTANT: All times are interpreted as UTC regardless of format. Accepts: 'YYYY-MM-DD HH:MM:SS' (UTC), 'YYYY-MM-DDTHH:MM:SSZ', 'MM/DD/YYYY HH:MM' (UTC), etc. Example: '2024-12-25 14:00:00' means 2:00 PM UTC, not local time. Must be in the future.

Output Schema

NameRequiredDescriptionDefault
dataYesRaw Mobile Text Alerts API response envelope. A scheduled send returns a confirmation message only — there is currently no nested `data` payload and no scheduled-message ID.
errorNo
noticeNoSomething the user should be told about this send, e.g. that it used a limited trial number
statusYes
contextNoAdditional context about why the call was blocked
successYes
sentFromNoThe number the message was sent from
errorCodeNoMachine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures.
nextStepsNoExplicit recovery guidance for the calling agent
statusTextYes
scheduledForNo
formattedPhoneNo
totalScheduledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Adds real context beyond the annotations: the default sending number is 'the one it last sent from' unless `from` overrides it, and the response's `sentFrom` reports which was used. However, with destructiveHint=true the description never acknowledges that the scheduled message will actually be dispatched and cannot be recalled, nor how to cancel it.

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?

Three compact sentences, front-loaded with what the tool does, then when to use it, then the one non-obvious behavior. No filler.

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?

Purpose, timing constraint, and the default-sender nuance are all covered, and the output schema covers return values. An agent has everything needed to call this correctly without opening the schema.

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% and already documents `from`'s default-number fallback, UTC interpretation, and the future-date requirement. The description restates the default-number rule and points at `sentFrom` in the response, but adds no new parameter semantics.

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 ('Schedule a message to be sent at a specific time in the future') and names the API it targets. It also implicitly distinguishes itself from send_message by contrasting 'later date/time rather than immediately'.

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?

Explicitly says when to use it: 'when you need to send a message at a later date/time rather than immediately,' which is the decision boundary against immediate sending. No explicit when-not or named alternative tool, so it stops short of a 5.

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