Skip to main content
Glama

Messaging: Send message

messaging_send_message
Destructive

Send a message in an existing LinkedIn, WhatsApp, Instagram, Facebook or Telegram chat. Supports text, base64 file attachments and provider-specific options. Locate/read the chat first if chat_id is not already known. This is a real external send action.

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": {
      "chat_id": "<chat_id>",
      "text": "<text>"
    },
    "name": "messaging_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
chat_idYesExact chat/conversation ID from the appropriate chat/inbox listing or resolver. Never pass a person name or user ID. Chat ID: Exact provider chat/conversation ID. LinkedIn chat IDs may also be visible in /messaging/thread/{chat_id}/ URLs. Obtain with: provider list conversations/inbox chats -> chat.id Never pass: person name, user_id, message_id.
specificsNo
account_idNoOptional Nilyo connection ID (unipile_account_id from list_connected_accounts). Omit when the user has one account for this provider. When several exist, Nilyo never guesses: list them (display name, identifier, provider user ID), choose the one the user named or ask, and pass its ID here.
attachmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, idempotentHint=false, so the risk profile is covered. The description adds a genuinely useful warning ('This is a real external send action') that reinforces irreversibility/externality, plus the base64 attachment mechanism. It does not address duplicate-send behavior or how a failed attachment is handled, which keeps it below a 5.

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?

Three short sentences, front-loaded with the core action and medium-specific support, with the prerequisite and the risk warning trailing. No filler; could only be tightened by folding the warning into the first sentence.

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

Completeness3/5

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

For a destructive, open-world, multi-provider send with a nested attachments object and no output schema, the description covers the what and a prerequisite but omits return shape (e.g., whether a message id comes back) and any attachment constraints. Adequate to invoke, not fully complete.

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?

Schema coverage is only 40%, with 'text', 'specifics', and 'attachments' undocumented in the schema. The description partially compensates by saying it 'Supports text, base64 file attachments and provider-specific options' and the chat_id guidance points at the right resolver, but it adds nothing on attachment size limits, send_mode/voice_note semantics, or what 'specifics' actually accepts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource ('Send a message in an existing ... chat') and enumerates the supported providers, plus the payload types (text, base64 attachments, provider options). It does not name the provider-specific siblings (whatsapp_send_message, linkedin_send_message) or the start-chat siblings it supersedes, so an agent must infer which of the many send tools to pick.

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

Usage Guidelines3/5

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

'Locate/read the chat first if chat_id is not already known' gives a prerequisite, and 'existing chat' implicitly excludes new-conversation flows. But it never names messaging_start_chat, messaging_find_chat_by_user, or messaging_resolve_recipient as the concrete alternatives, so the routing decision is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.