Skip to main content
Glama
wechat-localmind

wechat-localmind

by qilaidev

wechat_export_media

Read-onlyIdempotent

Export media attachments from permitted WeChat chats by message ID. Converts protected .dat files into standard image, voice, and document formats for offline access.

Instructions

Safely export local WeChat media attachments from allowed chats (automatically decoding .dat XOR / V1-V2 AES+XOR images to .jpg/.png, voice .silk/.aud, documents .pdf/.xlsx) by msg_id.

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": "wechat_export_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNoForce immediate SQLCipher decryption and SQLite snapshot refresh.
msg_idsYesList of target message msg_ids to export.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / fresh
      Added value: +{
      +  "default": false,
      +  "description": "Force immediate SQLCipher decryption and SQLite snapshot refresh.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real behavior beyond that: automatic .dat XOR / V1-V2 AES+XOR decoding into standard formats and a restriction to 'allowed chats'. It omits where exported files land and whether existing files are overwritten, which matters for an export that produces on-disk artifacts.

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?

One front-loaded sentence states purpose, scope, and decoding behavior with no filler beyond the mildly promotional 'Safely'. The parenthetical format list is long but informative rather than redundant.

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?

The tool produces files and has no output schema, so the description should say what the caller gets back or where artifacts are written; it does neither. It covers the decoding and scope aspects well but leaves the output contract and failure modes for disallowed chats unstated.

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 both msg_ids and fresh are already documented in the schema. The description only echoes the msg_id targeting and says nothing about fresh (forced SQLCipher decryption / snapshot refresh), so 3 is the correct baseline.

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 names a specific verb and resource ('export local WeChat media attachments ... by msg_id') and enumerates the decoded output types (.jpg/.png, .silk/.aud, .pdf/.xlsx). It is clearly distinct from the sibling tools, which list, fetch, and search rather than export 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 phrase 'from allowed chats' hints at a scope restriction, and 'by msg_id' implies this follows a message lookup, but the description never states when to choose this over a sibling or what happens for messages outside allowed chats. Usage is implied rather than spelled out.

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