Skip to main content
Glama

Message: Send voice note

message_send_voice_note
Destructive

Send an audio attachment as a native/playable voice note where the connected provider supports it (notably WhatsApp/Telegram). Resolve chat_id first. Provide padded base64 content + exact MIME type/filename. Uploads use multipart when the complete JSON exceeds 1 MiB; provider file limits still apply. Do not send the same voice note repeatedly after an uncertain timeout; read chat state first.

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_voice_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoOptional caption/text only when supported/requested.
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_typeYesAudio MIME type. WhatsApp voice notes expect Opus in OGG: audio/ogg (codecs=opus); MP3 is sent as a regular audio file.
content_base64YesBase64-encoded audio bytes, not a URL/path.
duration_secondsNoDuration of the audio in seconds when known (shown by the provider on the voice note).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true; the description earns credit for operationalizing the non-idempotency warning into an actionable rule about uncertain timeouts. It also discloses transport behavior (multipart when JSON exceeds 1 MiB) and provider-side file limits, which annotations cannot express. It stops short of describing what a successful send returns or permission/account requirements beyond the account_id schema note.

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 compact sentences, front-loaded with the capability and provider caveat, then prerequisites, then transport limits, then the retry-safety rule. Every sentence carries content; no filler or restatement of the title.

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?

For a 7-parameter, 4-required mutation tool with no output schema but full annotation coverage, the description covers provider support, id preparation, encoding format, upload path, size limits and duplicate-send hazards. An agent has enough to call it correctly without further lookups.

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 86%, so the schema already documents chat_id, content_type, content_base64, account_id and duration_seconds in detail; the baseline is 3. The description reinforces the chat_id resolution ordering and the padded-base64 requirement, but adds little MIME or format detail beyond what the schema already states.

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 an audio attachment as a native/playable voice note') and scopes it to providers that support the feature (WhatsApp/Telegram). It implicitly separates itself from generic media sending by distinguishing 'native/playable voice note' from a regular audio file, though it never names the sibling tool that sends non-voice attachments.

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?

Gives concrete preconditions ('Resolve chat_id first', 'Provide padded base64 content + exact MIME type/filename') and an explicit retry exclusion ('Do not send the same voice note repeatedly after an uncertain timeout; read chat state first'). It does not explicitly state when to prefer this over message_send_native_media or messaging_send_message, so routing among siblings still requires 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.