Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_audio

Send an audio message to a WhatsApp recipient using base64 data or a URL. Supports optional MIME type, reply-to, mentions, and view-once settings.

Instructions

Send an audio file message. Provide either data (base64) or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
dataNoBase64 encoded audio data
urlNoURL of the audio file
mimeTypeNoMIME type (auto-detected if omitted)
mentionsNo
replyToNoMessage ID to reply to
replyToSenderIdNo
isForwardedNo
viewOnceNo
ephemeralExpirationNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed18 schema fields changedv2.0.0
    • removedInput schema / properties / audioBase64
      Removed value: -{
-  "description": "Base64 encoded audio data (alternative to audioURL)",
-  "optional": true,
-  "type": "string"
-}
    • removedInput schema / properties / audioURL
      Removed value: -{
-  "description": "URL of the audio file to send (alternative to audioBase64)",
-  "optional": true,
-  "type": "string"
-}
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Base64 encoded audio data",
+  "type": "string"
+}
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / isForwarded / description
      Removed value: -"Whether the message should be marked as forwarded"
    • removedInput schema / properties / isForwarded / optional
      Removed value: -true
    • removedInput schema / properties / mentions / description
      Removed value: -"List of phone numbers to mention"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • changedInput schema / properties / mimeType / description
      Previous value: -"MIME type of the audio file"New value: +"MIME type (auto-detected if omitted)"
    • removedInput schema / properties / mimeType / enum
      Removed value: -[
-  "audio/mpeg",
-  "audio/mp3",
-  "audio/ogg",
-  "audio/wav"
-]
    • changedInput schema / properties / replyTo / description
      Previous value: -"ID of the message being replied to"New value: +"Message ID to reply to"
    • removedInput schema / properties / replyTo / optional
      Removed value: -true
    • addedInput schema / properties / replyToSenderId
      Added value: +{
+  "type": "string"
+}
    • changedInput schema / properties / to / description
      Previous value: -"Recipient phone number (with @s.whatsapp.net) or group ID (with @g.us)"New value: +"Recipient JID"
    • addedInput schema / properties / url
      Added value: +{
+  "description": "URL of the audio file",
+  "type": "string"
+}
    • removedInput schema / properties / viewOnce / description
      Removed value: -"Whether the audio should be sent as view-once"
    • removedInput schema / properties / viewOnce / optional
      Removed value: -true
    • changedInput schema / required
      Previous value: -[
-  "to",
-  "mimeType"
-]New value: +[
+  "to"
+]
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states to provide data or url, but does not mention what happens if both are supplied, file size limits, supported formats, or potential errors. The 'auto-detected if omitted' note for mimeType is in the schema, not description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) and to the point, but it lacks necessary detail. It is not wasteful, but it is under-specified for a tool with 10 parameters.

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 has 10 parameters, no output schema, and no annotations, the description is highly incomplete. It does not explain return values, error behavior, or how to use optional parameters. Essential context for agent usage is missing.

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

Parameters2/5

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

Schema coverage is 50%, meaning 5 parameters lack descriptions. The tool description adds no parameter-specific details beyond the schema. It mentions 'data' and 'url' but does not clarify their meaning or constraints. The description fails to compensate for missing schema descriptions.

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?

The description clearly states the action and resource: 'Send an audio file message.' It also notes the two ways to provide the audio (data or url), which differentiates it from other send tools like send_image or send_document. However, it could be more explicit about context (e.g., in a WhatsApp chat).

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 like send_voice (which might be for voice notes). There are no exclusions or prerequisites mentioned, leaving the agent without decision support.

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/wsapi-chat/wsapi-mcp'

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