Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

channel_getSubscribers

Retrieve subscribers of a WhatsApp channel from your contact list. Provide the channel ID and optional limit to get the list.

Instructions

[Channel Chat] Gets the subscribers of the channel (only those who are in your contact list)

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

Input Schema

NameRequiredDescriptionDefault
limitNoThe maximum number of subscribers to return
chatIdNoUnique WhatsApp id for the given channel group
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/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 does disclose a significant limitation: subscribers are limited to those in the agent's contact list. However, it doesn't mention permissions, pagination, return format, or the optional chatId parameter's role, so some behavioral traits remain hidden.

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 that efficiently communicates what the tool does and a key limitation. The '[Channel Chat]' prefix is minimal and adds useful categorization without clutter.

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

Completeness4/5

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

For a simple list tool with one required parameter and no output schema, the description covers the main purpose and an important constraint. It doesn't explain return format or authentication, but these can be reasonably inferred; overall it is fairly complete for its scope.

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 coverage is 100%, and each parameter has a description. The tool description adds no extra parameter-level meaning beyond what the schema already provides, so the baseline score of 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 clearly states the tool's function: 'Gets the subscribers of the channel' – a specific verb and resource. The qualifier 'only those who are in your contact list' adds scope clarity and distinguishes it from other channel-related tools like channel_getClassInfo or channel_fetchMessages.

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 implies using this tool when you need channel subscribers, but it does not explicitly state when to use it versus alternatives. It provides a constraint (contact list only) but no exclusions or mention of related tools, leaving timing considerations up to the agent.

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