Skip to main content
Glama
AgentPhone-AI

AgentPhone MCP Server

Official
by AgentPhone-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

send_message

Send SMS or iMessage from an agent's phone number, attach media, thread replies, add effects, or react to existing messages.

Instructions

Send an SMS or iMessage from one of your agent's phone numbers, or react to a message.

The agent must have at least one phone number attached. If the agent has multiple numbers, number_id or from_number selects which one to send from. iMessage extras (silently ignored on SMS): reply_to_message_id threads the reply under an earlier message, and send_style adds an expressive screen/bubble effect. To react to a message instead of sending one, set reaction and react_to_message_id (iMessage only); to_number and body are not needed in that case.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoThe message text to send (may be empty when sending media only)
agent_idNoThe agent ID to send from (the agent must have a phone number attached). Optional if you pass from_number or number_id instead.
reactionNoiMessage only. Tapback or single emoji applied to react_to_message_id: one of love, like, dislike, laugh, emphasize, question, or a single emoji (e.g. '🔥'). When set, this reacts instead of sending a message.
media_urlNoURL of a single image/media file to attach
number_idNoSpecific phone number ID to send from (if agent has multiple numbers)
to_numberNoRecipient: a phone number in E.164 format (e.g. +14155551234), a US short code, or a group ID (grp_...) to post into an iMessage group chat. Required when sending a message (not needed for a reaction).
media_urlsNoMultiple media URLs to attach (delivered as an image carousel on iMessage)
send_styleNoiMessage only. Expressive screen/bubble effect to send with the message
from_numberNoExact number to send from in E.164 format (alternative to number_id)
react_to_message_idNoiMessage only. ID of a message to react to. Set together with `reaction`.
reply_to_message_idNoiMessage only. ID of an earlier message to reply to inline (threaded reply)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare openWorldHint=true, so the description carries most of the burden and delivers real behavioral context: iMessage-only fields are 'silently ignored on SMS', reply_to_message_id threads a reply, and reaction mode changes which parameters are required. It omits permissions, delivery/failure behavior, and rate limits.

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?

Four short sentences, front-loaded with the send/extras/react structure; each sentence carries distinct information. Dense but readable, with no filler.

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

Completeness4/5

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

For an 11-parameter tool with zero required params and no output schema, the description covers the primary send path, the number-selection path, and the reaction path, which is what an agent needs to invoke it. Remaining gaps (single vs. carousel media, error surfaces) are minor.

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 baseline is 3, but the description adds cross-parameter conditional semantics the schema does not state on its own: number_id/from_number select the sending number, and to_number/body are explicitly unnecessary when reacting. It does not clarify media_url vs media_urls interaction.

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?

Specific verb and resource ('Send an SMS or iMessage') plus an explicit second mode ('or react to a message'), scoped to 'one of your agent's phone numbers'. An agent can immediately distinguish this from siblings like make_call or get_messages.

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?

States the prerequisite ('agent must have at least one phone number attached') and the selection rule when multiple numbers exist, plus when to switch to reaction mode instead of sending. It does not name sibling alternatives (e.g. make_call for voice), so it stops short of full routing guidance.

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