Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

whatsapp_send_media

Send media messages (image, video, audio, document, sticker) via WhatsApp by providing a media ID or URL along with authentication and recipient details.

Instructions

Send a media message (image, video, audio, document, sticker) via WhatsApp.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bearer_token": "<bearer_token>",
      "phone_number_id": "<phone_number_id>",
      "to": "<to>",
      "media_type": "<media_type>"
    },
    "name": "whatsapp_send_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
captionNo
filenameNoFor documents: the display filename
media_idNoID of a previously uploaded media object
media_linkNoURL of the media to send
media_typeYesimage, video, audio, document, or sticker
bearer_tokenYes
phone_number_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. The description does not disclose behavioral traits such as authentication requirements, handling of missing media_id/media_link, rate limits, or return behavior. It only states the basic action.

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 a single concise sentence, but it lacks necessary detail for a tool with 8 parameters. It is appropriately front-loaded but insufficient in content.

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's complexity (multiple media types, optional parameters, no output schema), the description is too brief. It does not cover important usage constraints like whether both media_id and media_link can be provided or what happens if neither is provided.

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?

Schema description coverage is 50% (4 of 8 parameters have descriptions). The description adds no parameter semantics, e.g., it doesn't explain the relationship between media_id and media_link, or when caption is applicable.

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 the action (send), resource (media message), and lists supported types (image, video, audio, document, sticker). It distinguishes from sibling tools like whatsapp_send_text, whatsapp_send_template, and whatsapp_upload_media.

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?

No guidance on when to use this tool vs alternatives like whatsapp_upload_media (for uploading first) or whatsapp_send_template. No context on prerequisites or exclusions.

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

Deploy Server

Other Tools