Skip to main content
Glama
wsapi-chat

WSAPI WhatsApp MCP Server

by wsapi-chat
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

whatsapp_send_sticker

Deliver WebP stickers to WhatsApp recipients by providing base64 data or a URL. Supports animated stickers, mentions, reply-to, and ephemeral expiration. Ideal for AI assistants automating sticker sending.

Instructions

Send a sticker message (WebP format). Provide either data (base64) or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient JID
dataNoBase64 encoded sticker data
urlNoURL of the sticker
isAnimatedNoWhether the sticker is animated
mentionsNo
replyToNo
replyToSenderIdNo
isForwardedNo
ephemeralExpirationNo

Schema Changelog

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

  1. Changed16 schema fields changedv2.0.0
    • addedInput schema / properties / data
      Added value: +{
+  "description": "Base64 encoded sticker data",
+  "type": "string"
+}
    • addedInput schema / properties / ephemeralExpiration
      Added value: +{
+  "enum": [
+    "off",
+    "24h",
+    "7d",
+    "90d"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / isAnimated / optional
      Removed value: -true
    • 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"
    • removedInput schema / properties / mentions / optional
      Removed value: -true
    • removedInput schema / properties / mimeType
      Removed value: -{
-  "description": "MIME type of the sticker (must be image/webp)",
-  "enum": [
-    "image/webp"
-  ],
-  "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"
+}
    • removedInput schema / properties / stickerBase64
      Removed value: -{
-  "description": "Base64 encoded sticker data (alternative to stickerURL)",
-  "optional": true,
-  "type": "string"
-}
    • removedInput schema / properties / stickerURL
      Removed value: -{
-  "description": "URL of the sticker to send (alternative to stickerBase64)",
-  "optional": true,
-  "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 sticker",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "to",
-  "mimeType"
-]New value: +[
+  "to"
+]
  2. First observed

TDQS

B3.2/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 full disclosure burden. It only states 'send' implying mutation, but fails to disclose side effects, authorization needs, rate limits, or response behavior. This is a significant gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) with no redundancy. It is efficient but under-informative for the tool's complexity.

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 no output schema, no annotations, and 9 parameters with limited descriptions, the description is incomplete. It lacks details on animated stickers, reply behavior, and error handling, failing to fully equip an AI agent for correct invocation.

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

Parameters2/5

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

With only 44% schema description coverage, the description should compensate but only mentions 'data' and 'url' as alternatives. It adds no meaning for parameters like isAnimated, mentions, replyTo, or ephemeralExpiration, leaving most parameters semantically barren.

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 explicitly states 'Send a sticker message (WebP format)', clearly identifying the action and resource. It distinguishes from sibling tools like whatsapp_send_image by specifying the WebP format requirement.

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?

The description mentions 'Provide either data (base64) or url', giving a basic usage hint. However, it does not specify when to use this tool over alternatives, prerequisites, or exclusions, relying on implied context.

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