whatsmcp

Follow Channel

wa_follow_channel

Follow a WhatsApp Channel from one of your accounts using its link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`account_id`	Yes	the account to follow from, as returned by wa_list_accounts
`channel_link`	Yes	the channel link (https://whatsapp.com/channel/…) or bare invite key

Output Schema

TableJSON Schema

Name	Required	Description
`items`	No	the rows of a list operation
`status`	Yes	ok (the operation succeeded) or refused (see refusal; for wa_update_group, applied lists the changes that took effect before it)
`applied`	No	wa_update_group only: the settings that were changed, in order — on a refusal, the ones that took effect before it
`refusal`	No	present only when status is refused
`summary`	No	a human-readable result
`group_jid`	No	the new group's JID (wa_create_group only) — use it as wa_send_message's 'to'
`invite_link`	No	the group's invite link (wa_create_group or wa_get_group_invite_link)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / refusal / properties / account_status

Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / account_status_reason

Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / since

Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}

First observedSep 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already disclose readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the agent knows this is a non-destructive, non-idempotent write. The description adds only that the follow is scoped to a specific account and driven by a link; it says nothing about required account state, rate limits, or what happens on a duplicate follow.

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?

A single front-loaded sentence with zero filler; the resource and the input mechanism appear immediately. Nothing could be removed without losing information.

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?

An output schema exists, so return values need no explanation, and the two required parameters are fully documented in-schema. What is missing is precondition context (paired/authenticated account) for a state-changing action, which is minor for such a simple tool.

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%: account_id documents the wa_list_accounts provenance and channel_link documents both accepted formats. The description's "using its link" and "from one of your accounts" merely paraphrase that, adding no syntax or format detail beyond the schema.

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 states a specific verb (Follow) and resource (WhatsApp Channel) and the mechanism (using its link), so the operation is unambiguous. It does not differentiate itself from adjacent siblings such as wa_list_channels or wa_join_group, but no sibling performs the same action, so the risk of confusion is low.

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?

"Follow a WhatsApp Channel from one of your accounts using its link" gives no when-to-use/when-not guidance, no prerequisites (must the account be paired? must you be an admin?), and never references the sibling that lists channels or the link-acquisition step. Usage must be inferred entirely.

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

All whatsmcp 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?