Skip to main content
Glama

whatsapp_send_document

Send a document to a WhatsApp number using a public URL. Optionally add a filename and caption.

Instructions

Send document/file via WhatsApp. phone: no '+'. document_url: public URL. filename/caption: optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
phoneYes
document_urlYes
filenameNo
captionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Adds specifics like phone number format (no '+') and document_url must be public URL, and filename/caption optional. But lacks info on file size limits, supported formats, or error handling behavior.

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?

Very concise; three sentences cover purpose and key constraints. Front-loaded with purpose, then parameter notes. No wasted words.

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?

With 4 parameters, 2 required, and an output schema present, the description provides minimal but essential info. Missing details on file size, supported formats, and possible errors, which could impact agent decision-making.

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 description coverage is 0%, so description must compensate. Explains phone format, document_url requirement, and optional fields. However, doesn't elaborate on document_url needing to be a direct download link or filename default behavior.

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?

States 'Send document/file via WhatsApp' clearly. Distinguishes from sibling tools like send_image, send_audio, but could be more specific about document types.

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 versus alternatives like whatsapp_send_text or whatsapp_send_link. No context about prerequisites or excluded scenarios.

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/gabriellopesdesouza2002/mcp-whatsapp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server