wwebjs-mcp

client_setAutoDownloadVideos

Toggle the auto-download flag to control whether videos are automatically downloaded in a WhatsApp session.

Instructions

[Client] Set auto load download videos flag

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": {
      "sessionId": "<sessionId>"
    },
    "name": "client_setAutoDownloadVideos"
  }
}

Input Schema

Name	Required	Description	Default
`flag`	No	Flag true/false
`sessionId`	Yes	Unique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'set flag' and does not explain whether the setting persists, requires an active session, affects future downloads, or what the response/errors look like. This is a notable gap for a mutating setter.

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 a single sentence with no filler or redundant content. It is front-loaded with the action and appropriately sized for a simple setter tool.

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 is simple and the schema fully documents its parameters, but there are no annotations or output schema, and the description omits side effects and usage context. This is a minimum viable description, adequate for understanding the basic purpose but leaving clear gaps about behavior and return values.

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?

The schema covers 100% of parameters with descriptions (flag as boolean, sessionId as string), so the baseline is 3. The description adds no additional parameter information, leaving the meaning of 'flag' to be inferred from the tool name rather than explicit explanation.

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 uses the specific verb 'Set' and names the resource 'auto load download videos flag', clearly indicating the tool controls video auto-download behavior. The mention of 'videos' distinguishes it from sibling tools like client_setAutoDownloadAudio and client_setAutoDownloadPhotos. However, it largely restates the tool name and could be more precise about what 'auto load download' means.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context such as requiring an active session. It simply states the action with no exclusions or comparisons to related setters.

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

Deploy Server