Skip to main content
Glama

Message: Send native media

message_send_native_media
Destructive

Send one media/file attachment using the provider's native rendering mode where supported. Resolve chat_id first. Provide padded base64 bytes; uploads use multipart when the complete JSON exceeds 1 MiB. Provider file limits still apply. Useful for inline image/video/native media; for WhatsApp multiple attachments may become separate provider messages, so this tool intentionally sends one attachment per call for predictable behavior.

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>",
      "content_base64": "<content_base64>",
      "content_type": "<content_type>",
      "filename": "<filename>"
    },
    "name": "message_send_native_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
chat_idYesExact chat.id resolved/listed for the destination conversation; never pass a person name/user_id here.
filenameYes
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.
content_typeYes
content_base64Yes

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?

Adds real context beyond the annotations: padded base64 input, multipart upload triggered when complete JSON exceeds 1 MiB, provider file limits still applying, and one-attachment-per-call semantics for predictable behavior on WhatsApp. It does not disclose auth requirements, error behavior, or anything about the response, but the transport-level detail is genuinely useful.

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?

Front-loaded with the verb and resource, then prerequisites, then encoding/transport constraints, then the rationale for one-per-call. Dense but every sentence carries information; the 'for predictable behavior' clause is slightly padded but earns its place by justifying the design.

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?

Covers the send path and the framing constraints, which is the core of a mutation tool with destructive/openWorld annotations. Still missing content_type format expectations, what the response returns (no output schema exists), and account_id selection behavior, which is nontrivial given multiple connections.

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 33%, so the description must compensate and only partly does. It clarifies content_base64 formatting ('padded base64 bytes') and the chat_id resolution order, but leaves content_type, filename, text, and account_id undocumented in either place.

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 specific verb and resource: send one media/file attachment using the provider's native rendering mode. It scopes the tool to exactly one attachment per call, which is a meaningful distinction. However, it never names the adjacent siblings (messaging_send_message, message_send_voice_note), so the agent must infer the boundary from the schema alone.

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?

Gives the prerequisite 'Resolve chat_id first' and a use case ('useful for inline image/video/native media'), plus an implicit exclusion of multi-attachment calls. But no alternative tool is named — nothing says to use message_send_voice_note for audio or messaging_send_message for text-only — so the when-vs-alternatives guidance is only implied.

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.