WSAPI WhatsApp MCP Server

whatsapp_send_link

Send a WhatsApp message with a custom link preview, including title, description, and thumbnail. Use it instead of plain text to control how shared URLs appear.

Instructions

Send a text message with a link preview (title, description and thumbnail). Use it instead of whatsapp_send_text when you want to control how the preview looks. Not idempotent. Returns the message ID.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Recipient JID
`url`	Yes	URL to include
`text`	Yes	Message text (max 4096 characters)
`title`	No	Link preview title
`replyTo`	No
`mentions`	No
`description`	No	Link preview description
`isForwarded`	No
`jpegThumbnail`	No	Base64 JPEG thumbnail
`replyToSenderId`	No
`ephemeralExpiration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv2.0.0Apr 30, 2026

changedInput schema / properties / description / description

Previous value: -"Description for the link preview (max 1000 characters)"New value: +"Link preview description"

removedInput schema / properties / description / optional
```
Removed value: -true
```

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
```

changedInput schema / properties / jpegThumbnail / description

Previous value: -"Base64 encoded JPEG thumbnail for the link preview"New value: +"Base64 JPEG thumbnail"

removedInput schema / properties / jpegThumbnail / optional
```
Removed value: -true
```

removedInput schema / properties / mentions / description

Removed value: -"List of phone numbers to mention in the message"

removedInput schema / properties / mentions / optional
```
Removed value: -true
```
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 / text / description

Previous value: -"Message text content (max 4096 characters)"New value: +"Message text (max 4096 characters)"

changedInput schema / properties / title / description

Previous value: -"Title for the link preview (max 500 characters)"New value: +"Link preview title"

removedInput schema / properties / title / optional
```
Removed value: -true
```

changedInput schema / properties / to / description

Previous value: -"Recipient phone number (with @s.whatsapp.net) or group ID (with @g.us)"New value: +"Recipient JID"

changedInput schema / properties / url / description

Previous value: -"URL to include in the message"New value: +"URL to include"

First observedSep 27, 2025

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotentHint=false, readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered; the description's 'Not idempotent' largely restates that. However, 'Returns the message ID' adds genuine value because there is no output schema, and it also hints the tool exposes preview-controlling fields.

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?

Three short sentences, each earning its place: purpose, alternative, and contract (non-idempotent + return value). The key distinguishing information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter, non-idempotent mutation tool with no output schema, the description covers purpose, routing and return value well, but leaves most optional parameters (reply threading, mentions, forwarding, ephemeral expiry) unexplained. Annotations carry the safety profile, so it is adequate but incomplete.

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 only 55% across 11 parameters, so several fields (replyTo, mentions, isForwarded, replyToSenderId, ephemeralExpiration) are undocumented anywhere. The description clarifies the preview-related params (title, description, thumbnail) but does not compensate for the coverage gap, so it sits at the baseline.

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?

Specific verb+resource plus the defining feature (link preview with title, description, thumbnail), and it explicitly contrasts itself with the sibling whatsapp_send_text. An agent can distinguish it from send_text, send_image, or send_document without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative (whatsapp_send_text) and the exact condition that should route the agent here: when you want to control how the preview looks. This is explicit when-to-use guidance tied to a named sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

whatsapp_send_link

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools