Skip to main content
Glama
Sign In
yehudashtein

wa-bridge-mcp

by yehudashtein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

download_media

Downloads media from a WhatsApp message and returns its local file path, so assistants can save attachments by message ID and chat JID.

Instructions

Download media from a WhatsApp message and get the local file path.

Args:
    message_id: The ID of the message containing the media
    chat_jid: The JID of the chat containing the message

Returns:
    A dictionary containing success status, a status message, and the file path if successful

Input Schema

NameRequiredDescriptionDefault
chat_jidYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses only the return dictionary shape; it says nothing about where files are written, overwrite behavior, size/time limits, or what happens when the message has no media — all material for a download operation.

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?

Front-loaded purpose sentence followed by a clean Args/Returns block, with no filler. Slightly formulaic but efficient and easy to scan.

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 simple two-parameter tool with no output schema, the description covers the essentials (what it does, params, return shape). It falls short on failure modes and file-path semantics, which an agent would need before relying on it.

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 the description must compensate. It does provide a one-line gloss per parameter, but these mostly restate the names ('The ID of the message containing the media'), adding only the minimal hint that the message must contain media.

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 ('Download media from a WhatsApp message') plus the concrete outcome ('get the local file path'). It is unambiguous what the tool does, though it never distinguishes itself from siblings like get_message_context or send_file.

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 when-to-use guidance is given — nothing about needing to resolve a message_id first (e.g., via list_messages or get_message_context), and no alternatives or exclusions are named. The agent must infer the workflow entirely.

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