Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_image

Send an image message to a WhatsApp recipient using base64 data or image URL. Supports caption, mentions, reply, forwarding, view-once, and ephemeral expiration settings.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
dataNoBase64 encoded image data
urlNoURL of the image
mimeTypeNoMIME type (auto-detected if omitted)
captionNoCaption for the image
mentionsNoJIDs of mentioned users
replyToNoMessage ID to reply to
replyToSenderIdNoSender JID of the replied message
isForwardedNoMark as forwarded
viewOnceNoSend as view-once
ephemeralExpirationNo

Schema Changelog

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

  1. Changed20 schema fields changedv2.0.0
    • changedInput schema / properties / caption / description
      Previous value: -"Caption for the image (max 1024 characters)"New value: +"Caption for the image"
    • removedInput schema / properties / caption / optional
      Removed value: -true
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Base64 encoded image data",
+  "type": "string"
+}
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / imageBase64
      Removed value: -{
-  "description": "Base64 encoded image data (alternative to imageURL)",
-  "optional": true,
-  "type": "string"
-}
    • removedInput schema / properties / imageURL
      Removed value: -{
-  "description": "URL of the image to send (alternative to imageBase64)",
-  "optional": true,
-  "type": "string"
-}
    • changedInput schema / properties / isForwarded / description
      Previous value: -"Whether the message should be marked as forwarded"New value: +"Mark as forwarded"
    • removedInput schema / properties / isForwarded / optional
      Removed value: -true
    • changedInput schema / properties / mentions / description
      Previous value: -"List of phone numbers to mention in the caption"New value: +"JIDs of mentioned users"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • changedInput schema / properties / mimeType / description
      Previous value: -"MIME type of the image"New value: +"MIME type (auto-detected if omitted)"
    • removedInput schema / properties / mimeType / enum
      Removed value: -[
-  "image/jpeg",
-  "image/png",
-  "image/webp",
-  "image/gif"
-]
    • 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: +{
+  "description": "Sender JID of the replied message",
+  "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 image",
+  "type": "string"
+}
    • changedInput schema / properties / viewOnce / description
      Previous value: -"Whether the image should be sent as view-once"New value: +"Send 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

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the basic action and parameter requirement, omitting behavioral traits such as permissions needed, what happens if both data and url are provided, or side effects like overwriting existing messages.

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, concise sentence that directly conveys the core purpose and key parameter constraint. No unnecessary words.

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?

With 11 parameters and no output schema, the description is too brief. It mentions only the image source requirement, ignoring optional parameters like caption, mentions, and replyTo, and does not describe the return value or behavior when multiple image sources are provided.

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 description coverage is 91%, so the schema already documents most parameters. The description adds minimal value by emphasizing the data/url requirement, but does not explain interactions or constraints beyond that.

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 'Send an image message', which is a specific verb+resource. It distinguishes from sibling tools like whatsapp_send_audio or whatsapp_send_text by specifying the media type.

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?

It provides basic guidance on how to provide the image ('Provide either data (base64) or url'), but lacks guidance on when to use this tool versus alternatives like whatsapp_send_document for images, or context about prerequisites.

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