Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_document

Send a document file to a WhatsApp recipient using base64 data or a direct URL. Requires recipient ID and filename. Supports optional caption, mentions, reply-to, and expiry settings.

Instructions

Send a document file. Provide either data (base64) or url. Filename is required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
dataNoBase64 encoded document data
urlNoURL of the document
filenameYesFilename shown to recipient
mimeTypeNoMIME type (auto-detected if omitted)
captionNoCaption for the document
mentionsNo
replyToNo
replyToSenderIdNo
isForwardedNo
ephemeralExpirationNo

Schema Changelog

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

  1. Changed19 schema fields changedv2.0.0
    • changedInput schema / properties / caption / description
      Previous value: -"Caption for the document (max 1024 characters)"New value: +"Caption for the document"
    • removedInput schema / properties / caption / optional
      Removed value: -true
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Base64 encoded document data",
+  "type": "string"
+}
    • removedInput schema / properties / documentBase64
      Removed value: -{
-  "description": "Base64 encoded document data (alternative to documentURL)",
-  "optional": true,
-  "type": "string"
-}
    • removedInput schema / properties / documentURL
      Removed value: -{
-  "description": "URL of the document to send (alternative to documentBase64)",
-  "optional": true,
-  "type": "string"
-}
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / fileName
      Removed value: -{
-  "description": "Name of the document file (max 255 characters)",
-  "type": "string"
-}
    • addedInput schema / properties / filename
      Added value: +{
+  "description": "Filename shown to recipient",
+  "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
    • addedInput schema / properties / mimeType
      Added value: +{
+  "description": "MIME type (auto-detected if omitted)",
+  "type": "string"
+}
    • removedInput schema / properties / replyTo / description
      Removed value: -"ID of the message being replied 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 document",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "to",
-  "fileName"
-]New value: +[
+  "to",
+  "filename"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, and description gives minimal behavioral context. Does not disclose side effects, required permissions, success/failure behavior, or rate limits. The one-line description does little to explain what happens when sending.

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?

Highly concise: two sentences, front-loads the action. No wasted words, every part earns its place.

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 far too brief. Ignores many optional parameters (caption, mentions, etc.) and does not explain the expected behavior beyond the basic action.

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?

Description clarifies that 'data' and 'url' are alternatives and 'filename' is required. With schema coverage at 55%, this adds some value but not enough to fully compensate for the other parameters left unexplained.

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?

Clearly states the action 'Send a document file' and the resource. Distinguishes from siblings like whatsapp_send_image via naming and scope.

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?

Provides explicit guidance on providing either base64 data or a URL, and that filename is required. However, no when/why to choose this over other sending tools beyond name.

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