Wassenger

manage_whatsapp_channels

Comprehensive WhatsApp channel management tool supporting all channel operations. Perfect for managing channel lifecycle, membership, and content. Supports all WhatsApp channel operations through a unified action-based interface.

Available actions:

list: List and retrieve channels with filtering options
get: Get detailed information about a specific channel
create: Create new channels with optional profile images
update: Update existing channel information (name, description)
search: Search for public channels by category and keywords
join: Join/follow channels via invite code or URL
leave: Leave/unfollow channels
delete: Delete channels (alias for leave)
update_image: Update channel profile images

Input Schema

Name	Required	Description
`name`	No	Channel name (required for create, optional for update)
`page`	No	Page number for pagination (0-based)
`sort`	No	Sort field and order (e.g., "-createdAt", "name")
`limit`	No	Number of results to retrieve (max 250)
`action`	Yes	Action to perform on WhatsApp channels
`device`	Yes	WhatsApp device ID connected to Wassenger (24 character hexadecimal string)
`include`	No	Include related entities in response
`category`	No	Category of channels to search for (for search action)
`imageUrl`	No	URL of image to use as channel profile picture (JPG or PNG, max 1MB)
`channelId`	No	WhatsApp channel ID (required for get, update, leave, delete, update_image actions)
`countries`	No	Country codes to filter channels by (e.g., ["US", "GB"])
`imageData`	No	Base64-encoded image data (JPG or PNG, max 1MB)
`inviteUrl`	No	Channel invitation URL (required if joinMethod is "url")
`sortField`	No	Field to sort search results by
`sortOrder`	No	Sort order for search results
`inviteCode`	No	Channel invitation code (required if joinMethod is "code")
`joinMethod`	No	Method to join the channel (for join action)
`permission`	No	Filter channels by permission type (for list action)
`description`	No	Channel description (up to 2048 characters)
`imageSource`	No	Source type for channel image
`searchQuery`	No	Text to search for in channel names and descriptions (for search action)
`uploadImage`	No	Whether to upload a profile image (for create action)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It names destructive operations like delete and leave but does not disclose permissions, reversibility, side effects, rate limits, or what happens to channel content on delete; the note that delete is an alias for leave adds some context but is not enough for a 22-parameter mutation tool.

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

Conciseness3/5

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

The action list is useful and front-loaded, but the opening two sentences are repetitive: “Comprehensive WhatsApp channel management tool supporting all channel operations” is immediately restated. The content is appropriately sized for a unified action tool, but it could be tightened.

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

Completeness2/5

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

This is a large unified tool with 22 parameters, no output schema, and no annotations, yet the description does not cover permissions, side effects, return values, or preconditions. The action list helps, but important operational context is missing for safe 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 schema already documents all parameters extensively. The description adds useful action-level mapping, such as create using profile images, search using category/keywords, and join using invite code or URL, but it does not add significant per-parameter meaning beyond the schema descriptions.

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 that this is a WhatsApp channel management tool and enumerates the supported channel operations, so the verb and resource are specific. It does not distinguish itself from sibling channel tools such as manage_whatsapp_channel_messages, but the channel-management scope is clear.

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 available actions list implies when each operation is relevant, but there is no explicit guidance on when to use this tool versus siblings, no prerequisites, and no warnings about destructive operations such as delete/leave. The action list is helpful but is not a full usage policy.

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

All Wassenger tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?