Skip to main content
Glama
pauloFroes

mcp-meta-inbox

by pauloFroes

Send Message

send_message

Send a direct message from your Facebook Page to a person on Messenger or Instagram Direct. Works only within 24 hours of the user's last message to the Page.

Instructions

Send a direct message from the Page to a person, on Messenger or Instagram Direct. This publishes to a real person's inbox — confirm the recipient and the text with a human before calling it. Meta only allows a free-form reply within 24 hours of that person's last message; outside that window the call fails and a message tag or paid channel is required. Instagram Direct additionally requires Advanced Access to instagram_manage_messages (App Review). Without it Meta answers with a ~27s timeout, subcode 2534084. Instagram comments are NOT affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage body to send.
image_urlNoOptional publicly reachable image URL to send instead of text.
recipient_idYesThe recipient's Page-scoped ID (PSID) on Messenger, or IGSID on Instagram. Take it from the participant entry in get_conversation, or from the comment author in list_comments.
Behavior5/5

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

Goes beyond annotations by disclosing that it publishes to a real person's inbox, the 24-hour window constraint, and Instagram's Advanced Access requirement. Annotations already indicate write operation (not read-only) but description adds crucial failure context.

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-structured with main action first, then safety warning, then constraints, then Instagram specifics. Every sentence adds value, though it could be slightly more concise; still efficient for the information density.

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?

Thorough coverage of a complex tool (two channels, permissions, time windows, failure modes) despite no output schema. Addresses all necessary context for an agent to use safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds value beyond 100% schema coverage by explaining how to obtain recipient_id (from get_conversation or list_comments) and implying mutual exclusivity of text and image_url. Schema descriptions are present but description provides practical sourcing and usage context.

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?

Clearly states the action (send), the resource (direct message), and the channels (Messenger or Instagram Direct). Distinguishes from siblings like private_reply and comment-related tools by explicitly saying 'Instagram comments are NOT affected.'

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?

Provides explicit when-to-use (within 24-hour window), when-not-to-use (outside window requires message tag or paid channel), and safety advice (confirm with human). Also details Instagram Direct permissions and failure mode (timeout, subcode).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pauloFroes/mcp-meta-inbox'

If you have feedback or need assistance with the MCP directory API, please join our Discord server