send_sms

Prepares one SMS for the signed-in user. This does not send the text.

Use with an AI agent

Export this page as Markdown or bundle it with a task for your agent.

Try a task
Preview the prompt that will be copied

Access

  • Effect: Changes data
  • Required scope: write (the mcp scope also grants it)

Example request

The JSON-RPC message an MCP client sends to call this tool. Your client builds it for you; this is for reference and debugging in a tool such as MCP Inspector.

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

Example IDs refer to fictional demo data. Replace them with IDs from your account before calling the real server.

Description

Prepares one SMS for the signed-in user. This does not send the text.

Call when the user clearly wants a text sent now — including direct asks ("text +1…") and obvious send intents ("tell Sarah I'll be 15 minutes late") once you have a usable number and body. For soft signals ("I haven't talked to John"), offer a draft first; call this only after they want you to prepare it. Compose message as a short natural SMS that keeps their meaning (no stiff AI phrasing).

To revise a pending draft, pass reviseActionId from get_pending_sms or the prior send_sms result plus the updated fields. That replaces the draft, returns a new actionId, and invalidates the old one — an old yes must not approve the new body. Omitting reviseActionId while a draft exists also replaces it; prefer reviseActionId when editing so stale IDs fail closed.

Pass recipientPhoneNumber only when the user supplied one E.164 number. For "text me", set useMyPhoneNumber true and omit the number. If they name a person and do not give a number, pass recipientLabel and omit the number; do not invent one. One recipient. If they name several numbers, ask which one instead of calling.

status awaiting_confirmation includes actionId, deliveryState awaiting_confirmation, and the exact number and body. replacedActionId is set when a prior draft was superseded. Nothing is sent until confirm_send_sms opens a client confirmation prompt for the new actionId and the user accepts it. After a successful send, a new request needs a new send_sms and a new confirmation.

Input parameters

NameTypeRequiredDescription
messagestringNo
recipientLabelstringNo
recipientPhoneNumberstringNo
reviseActionIdstringNo
useMyPhoneNumberbooleanNo
Full input schema (JSON Schema)
json
{
  "additionalProperties": false,
  "properties": {
    "message": {
      "type": "string"
    },
    "recipientLabel": {
      "type": "string"
    },
    "recipientPhoneNumber": {
      "type": "string"
    },
    "reviseActionId": {
      "type": "string"
    },
    "useMyPhoneNumber": {
      "type": "boolean"
    }
  },
  "type": "object"
}