wwebjs-mcp

channel_setProfilePicture

Set a new profile picture for a WhatsApp channel by specifying the channel ID and either an image URL or media file.

Instructions

[Channel Chat] Update a channel profile picture

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

Input Schema

Name	Required	Description
`chatId`	No	Unique WhatsApp id for the given channel group
`sessionId`	Yes	Unique identifier for the session (alphanumeric and - allowed)
`newProfilePictureUrl`	No	New profile picture URL for the channel
`newProfilePictureMedia`	No	New profile picture media for the channel

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.4/5.0

Behavior1/5

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

Annotations are absent, so the description must carry the full burden of behavioral disclosure. It simply restates the tool name without revealing side effects, permission requirements, parameter interactions, or reversibility. For a mutation tool, this is a severe transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but under-specified rather than concise. It merely paraphrases the tool name and provides no additional context. The single sentence does not earn its place because it offers no information beyond the resource and action already implied by the name.

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

Completeness1/5

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

Without annotations or an output schema, a complete description should explain permissions, parameter usage, and behavioral effects. This description does none of that. The presence of a nested object (newProfilePictureMedia) and optional parameters makes the tool non-trivial, and the description is wholly inadequate for guiding correct invocation.

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 baseline is 3. The description itself adds no parameter-level insight, but the schema already provides basic descriptions for each parameter. However, the relationship between newProfilePictureUrl and newProfilePictureMedia remains ambiguous, which the description does not clarify.

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 clearly states the action (update) and resource (channel profile picture), making its purpose obvious. The '[Channel Chat]' prefix helps distinguish it from similar tools like client_setProfilePicture and groupChat_setPicture. However, it adds little beyond what the tool name itself conveys.

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. It does not mention required permissions, whether to use newProfilePictureUrl vs newProfilePictureMedia, or any exclusions that would help an agent decide between competing tools.

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

Deploy Server