Skip to main content
Glama
Sign In
whatsapp-localmind

whatsapp-localmind

by qilaidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

whatsapp_export_media

Export local WhatsApp group media attachments by message ID to the shared snapshot/media directory and return absolute file paths.

Instructions

Safely export local WhatsApp group media attachments (voice .opus, documents .pdf/.xlsx, images) by msg_id to the shared snapshot/media directory and return absolute file paths.

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": {
      "msg_ids": "<msg_ids>"
    },
    "name": "whatsapp_export_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
msg_idsYesList of target message msg_ids to export.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that media is exported to a shared snapshot/media directory and that absolute file paths are returned, but it omits important behavior such as overwrite handling, permission requirements, missing-media errors, and whether non-group chats are supported.

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 definition is a single front-loaded sentence with no wasted wording. It conveys the action, supported media types, destination, and return value efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with no output schema, the description is largely complete: it explains the export destination and return format. Minor gaps around overwrite behavior and failure conditions keep it from being fully complete.

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 100%, so the sole msg_ids parameter is already documented in the schema. The description reinforces that export is by msg_id but adds no format, ordering, or validation semantics beyond the schema.

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 (export) and resource (WhatsApp group media attachments), including the supported file types and destination directory. It clearly distinguishes exporting media from listing groups or fetching/searching messages, though it does not explicitly name sibling tools.

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?

Usage is only implied by 'by msg_id'; there is no explicit guidance on when to use this tool versus fetching or searching messages, nor any note on how to obtain valid msg_ids or when export would fail. No alternatives or exclusions are provided.

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