Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_link

Send a link message with an optional rich preview, including title, description, and thumbnail, to provide context and improve engagement in WhatsApp chats.

Instructions

Send a link message with optional preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
textYesMessage text (max 4096 characters)
urlYesURL to include
titleNoLink preview title
descriptionNoLink preview description
jpegThumbnailNoBase64 JPEG thumbnail
mentionsNo
replyToNo
replyToSenderIdNo
isForwardedNo
ephemeralExpirationNo

Schema Changelog

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

  1. Changed17 schema fields changedv2.0.0
    • 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"
  2. First observed

TDQS

C2.8/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 behavioral traits. It only states the basic action and optional preview, omitting side effects, required permissions, or limitations (e.g., does the preview generate automatically?). This leaves significant ambiguity.

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 concise (one sentence) but lacks necessary detail. It is front-loaded with the action, but the brevity results in under-specification. A bit more structure (e.g., listing key optional features) would improve it.

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 11 parameters (many optional) and no output schema, the description is insufficient. It does not explain message behavior like mentions, reply chain, forwarding, or ephemeral settings. For a tool with this complexity, more context is needed.

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?

The input schema already describes most parameters (55% coverage). The description hints at preview-related parameters ('optional preview') but adds no new insight beyond the schema. For parameters like mentions, replyTo, etc., no extra context is provided.

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 ('Send a link message') and mentions the optional preview feature, distinguishing it from other send tools like whatsapp_send_text or whatsapp_send_image. However, it could be more specific about what constitutes a link message versus sending a plain text with a URL.

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. With numerous sibling send tools (e.g., whatsapp_send_text, whatsapp_send_image), explicit context about when to choose send_link would be beneficial.

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