Skip to main content
Glama
mark-o298

Respond.io MCP Server

by mark-o298

send_message

Send a message to a contact via a specified channel, supporting text, attachments, WhatsApp templates, emails, and quick replies.

Instructions

Send a message to a contact through a specific channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoThe message text, required for 'text' and 'email' message types.
subjectNoThe email subject, required for 'email' message types.
channelIdNoThe channel ID to send the message from. If null, the last interacted channel will be used.
identifierYesThe contact's identifier. Can be the contact's ID, email, or phone number.
messageTypeYesThe type of message to send.
templateNameNoThe name of the WhatsApp template, required for 'whatsapp_template' message types.
attachmentUrlNoThe URL of the attachment, required for 'attachment' message types.
attachmentTypeNoThe type of the attachment.
templateLanguageNoThe language code of the WhatsApp template, e.g. 'en', 'en_US'.
templateComponentsNoDynamic components for the WhatsApp template. Use this to fill in variable values ({{1}}, {{2}}, etc.) in the template body, header, or buttons. Example: [{ type: 'body', parameters: [{ type: 'text', text: 'John' }, { type: 'text', text: 'ORDER-123' }] }]. Omit if the template has no dynamic variables.
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states the tool 'sends a message' without noting side effects like triggering notifications, cost implications, rate limits, or whether it is idempotent. The agent gains little insight into the tool's operational behavior.

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?

The description is a single, clear sentence with no extraneous words. It is highly concise and efficiently communicates the tool's fundamental purpose.

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

Completeness2/5

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

Given the tool's complexity (10 parameters, no output schema, no annotations), the description is severely lacking. It does not explain return values, error handling, or prerequisites. The agent would need to infer or trial-and-error many details.

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?

The input schema has 100% description coverage, with each parameter already well-documented. The description adds no additional meaning beyond what the schema provides, so a baseline score of 3 is appropriate.

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?

The description clearly states the action 'Send', the resource 'a message', the recipient 'to a contact', and delivery method 'through a specific channel'. It unequivocally identifies the tool's purpose and distinguishes it from sibling tools like list_messages and get_message.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites, limitations, or exclusions mentioned. The description does not help the agent decide when this tool is appropriate.

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/mark-o298/respondio-mcp-server'

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