Skip to main content
Glama
Sign In
yehudashtein

wa-bridge-mcp

by yehudashtein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

send_file

Send pictures, raw audio, video, or documents via WhatsApp to a phone number or group JID by specifying the recipient and absolute file path.

Instructions

Send a file such as a picture, raw audio, video or document via WhatsApp to the specified recipient. For group messages use the JID.

Args:
    recipient: The recipient - either a phone number with country code but no + or other symbols,
             or a JID (e.g., "123456789@s.whatsapp.net" or a group JID like "123456789@g.us")
    media_path: The absolute path to the media file to send (image, video, document)

Returns:
    A dictionary containing success status and a status message

Input Schema

NameRequiredDescriptionDefault
recipientYes
media_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 the full burden of behavioral disclosure. It mentions the return shape and media types, but omits important operational details such as permissions, external side effects, file-size limits, recipient validation, or failure behavior.

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?

The description is front-loaded with the core action, followed by structured Args and Returns sections. Every part contributes to invocation understanding without unnecessary repetition or bloat.

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 a tool with no annotations and no output schema, the description explains parameters and return shape reasonably well. However, it leaves out behavioral prerequisites and constraints that matter for a send operation, such as authentication, file limits, and error conditions.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does: recipient is explained as either a phone number without symbols or a JID, including group JID examples, and media_path is described as an absolute path with file types. It could add whether media_path must already exist or whether URLs are accepted, but the parameter meaning is substantially clarified.

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 states a specific verb and resource: send a file via WhatsApp to a specified recipient. It also names supported media types and group JID behavior. It is clear but does not explicitly distinguish this from the overlapping sibling send_audio_message, which also handles audio media.

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 gives useful context that group messages require a JID, but it does not explain when to use send_file instead of send_message or send_audio_message. The usage is implied rather than explicitly guided with alternatives 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