Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

channel_transferChannelOwnership

Transfer WhatsApp channel ownership to another user. The new owner must already be a channel admin. Provide the chat ID and new owner ID.

Instructions

[Channel Chat] Transfers a channel ownership to another user. Note: the user you are transferring the channel ownership to must be a channel admin

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_transferChannelOwnership"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatIdNoUnique WhatsApp id for the given channel group
optionsNoOptions for transferring a channel ownership to another user
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)
newOwnerIdNoThe ID of the user to transfer ownership to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It adds a useful behavioral note about the admin requirement, but does not disclose side effects like what happens to the current owner's role, or the meaning/impact of options like shouldDismissSelfAsAdmin.

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 two sentences, with the core purpose upfront. The added note is relevant and necessary. Every word earns its place without redundancy.

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?

While the schema covers parameters and the description states the core action, the tool is a mutation with no output schema and no annotations. It lacks details about return values, success/failure behavior, or the effect of the shouldDismissSelfAsAdmin option. For a simple transfer tool, this is adequate but with clear gaps.

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 individual parameters like chatId and newOwnerId are already documented. The description's note about the new owner being a channel admin adds context for newOwnerId, but does not explain the nested options object's fields beyond examples. Baseline 3 is appropriate.

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 uses a specific verb ('Transfers'), a clear resource ('channel ownership'), and defines the exact action ('to another user'). This unambiguously distinguishes it from sibling tools like channel_demoteChannelAdmin or channel_sendChannelAdminInvite.

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 description gives a critical precondition (the new owner must be a channel admin), which implies when the tool can be used. However, it does not explicitly state when to use this over alternatives, nor any exclusions or when-not scenarios.

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