Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_video

Send a video message to a WhatsApp recipient using base64 data or a URL. Supports captions, mentions, reply-to, view-once, and expiration settings.

Instructions

Send a video message. Provide either data (base64) or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
dataNoBase64 encoded video data
urlNoURL of the video
mimeTypeNoMIME type (auto-detected if omitted)
captionNoCaption for the video
mentionsNo
replyToNoMessage ID to reply to
replyToSenderIdNoSender JID of the replied message
isForwardedNo
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 video (max 1024 characters)"New value: +"Caption for the video"
    • removedInput schema / properties / caption / optional
      Removed value: -true
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Base64 encoded video 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 in the caption"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • changedInput schema / properties / mimeType / description
      Previous value: -"MIME type of the video"New value: +"MIME type (auto-detected if omitted)"
    • removedInput schema / properties / mimeType / enum
      Removed value: -[
-  "video/mp4",
-  "video/3gp",
-  "video/mov",
-  "video/avi"
-]
    • 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 video",
+  "type": "string"
+}
    • removedInput schema / properties / videoBase64
      Removed value: -{
-  "description": "Base64 encoded video data (alternative to videoURL)",
-  "optional": true,
-  "type": "string"
-}
    • removedInput schema / properties / videoURL
      Removed value: -{
-  "description": "URL of the video to send (alternative to videoBase64)",
-  "optional": true,
-  "type": "string"
-}
    • changedInput schema / properties / viewOnce / description
      Previous value: -"Whether the video 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, and the description only mentions the basic action and input options. It omits important behavioral details such as permissions, limits, conflicting inputs, or error handling.

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 concise with two sentences, no filler, and front-loads the key action.

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 11 parameters and no output schema or annotations, the description lacks detail on many parameters and does not explain return values or side effects.

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

Parameters4/5

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

The description adds value beyond the schema by clarifying the mutual exclusivity of 'data' and 'url'. Schema coverage is 73%, but this constraint is not captured in individual parameter descriptions.

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 a video message', specifying the verb and resource. It also mentions providing data or url, which distinguishes it from other send tools.

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?

The description provides no guidance on when to use this tool versus alternatives like whatsapp_send_image or whatsapp_send_audio. It only states the requirement of providing data or url.

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