Skip to main content
Glama
textbee-mcp

textbee-mcp

Official

Send SMS

send_sms

Send an SMS to one or more phone numbers or short codes through your own textbee account and Android phone, with optional scheduling and SIM selection.

Instructions

Send an SMS through the user's own textbee account and Android phone. Recipients are phone numbers or short codes, sent as the user gives them. A local number or short code reaches recipients in the sending phone's country. For a number in another country, use international format with the country code, such as +15550100123. Sender names such as MYBANK cannot receive SMS. The sending phone is chosen automatically: the account default device, otherwise the enabled device with the most recent heartbeat. Only pass device_id when the user explicitly names a phone; ids come from list_devices. Sending costs the user a real message against their textbee plan quota, so do not send speculatively and do not retry a send that may already have gone out. When the account has SMS queueing enabled the result includes an sms_batch_id; pass it to get_messages as sms_batch_id to check per-recipient delivery status.

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": {
      "message": "<message>",
      "recipients": "<recipients>"
    },
    "name": "send_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe SMS body, plain text. Long messages are split into segments by the carrier and each segment counts against the quota; the result reports the segment count.
device_idNoWhich registered phone sends the message. Omit in almost every case and let textbee choose. Pass it only when the user asks for a specific phone. Ids come from list_devices.
recipientsYesPhone numbers or short codes, as the user gives them, for example ["5550100123"] or ["+15550100123"]. Do not add a country code or ask for one when the user gives a local number. Each recipient counts as one message. The plan caps how many recipients one send may have; the server rejects the send beyond it.
sim_numberNoWhich SIM sends the message: 1 for SIM 1, 2 for SIM 2. Omit to use the phone's default SIM.
scheduled_atNoISO 8601 timestamp to send later instead of now, for example 2026-09-01T14:30:00Z. Must be in the future, and requires the account's server to have queueing enabled. Omit to send immediately.
sim_subscription_idNoOlder option. The Android id of a SIM. It can change after a SIM swap, and a wrong value is silently ignored. Prefer sim_number. If both are given, only sim_number is used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • changedInput schema / properties / recipients / description
      Previous value: -"Phone numbers or short codes. Prefer international format with the country code, for example [\"+15550100123\"]. Use a local number or short code only when the user gives one. Each recipient counts as one message. The plan caps how many recipients one send may have; the server rejects the send beyond it."New value: +"Phone numbers or short codes, as the user gives them, for example [\"5550100123\"] or [\"+15550100123\"]. Do not add a country code or ask for one when the user gives a local number. Each recipient counts as one message. The plan caps how many recipients one send may have; the server rejects the send beyond it."
    • addedInput schema / properties / sim_number
      Added value: +{
      +  "description": "Which SIM sends the message: 1 for SIM 1, 2 for SIM 2. Omit to use the phone's default SIM.",
      +  "maximum": 8,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / properties / sim_subscription_id / description
      Previous value: -"Which SIM sends on a dual-SIM phone. The server does not validate this: a wrong value is silently ignored and the phone default SIM is used. The id is shown in the textbee Android app."New value: +"Older option. The Android id of a SIM. It can change after a SIM swap, and a wrong value is silently ignored. Prefer sim_number. If both are given, only sim_number is used."
  2. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / recipients / description
      Previous value: -"Phone numbers in international E.164 format including the country code, for example [\"+15550100123\"]. Each recipient counts as one message. The plan caps how many recipients one send may have; the server rejects the send beyond it."New value: +"Phone numbers or short codes. Prefer international format with the country code, for example [\"+15550100123\"]. Use a local number or short code only when the user gives one. Each recipient counts as one message. The plan caps how many recipients one send may have; the server rejects the send beyond it."
  3. First observedv0.0.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the lower bar applies — yet the description adds real operational context: the send consumes a real message against the plan quota, retries risk duplicate sends, sender-name recipients cannot receive, and phone selection falls back from account default to most-recent-heartbeat enabled device. It also discloses the conditional sms_batch_id in the result, which no annotation covers.

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?

Well front-loaded: what it does, then recipient formatting, then device selection, then cost caution, then result handling. Every sentence carries actionable information, though it is on the long side and a few points (sender names, heartbeat fallback) could be tightened without losing meaning.

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?

For a non-idempotent, cost-bearing, open-world send with six parameters and no output schema, the description covers the gaps that matter: quota cost, duplicate-send risk, device selection logic, recipient formatting, and how to verify delivery afterward. An agent has enough to call this correctly on the first attempt.

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 coverage is 100%, so the baseline is 3; the description earns above that by adding meaning the schema lacks — the country-code rule for recipients (don't add one to a local number), the reason to prefer sim_number over sim_subscription_id, and the user-intent trigger for device_id. It does not explain scheduled_at vs. queueing prerequisites in depth, but the schema already carries those.

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 (send) and resource (SMS via the user's textbee account and Android phone), and immediately disambiguates the resource model: recipients are phone numbers or short codes. It also names the sibling tools (list_devices for ids, get_messages for status), so an agent can distinguish it from read-side siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when/when-not guidance is given for the main decision points: omit device_id unless the user names a phone, use international format only for foreign numbers, and don't send speculatively or retry an ambiguous send. It also routes follow-up work to a named alternative (get_messages with sms_batch_id), which is the exact condition that selects it.

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

Deploy Server

Other Tools