Skip to main content
Glama
Sign In

WhatsApp Business API by Wassenger

by com.wassenger
OverviewDiscussionsAdmin

manage_whatsapp_contact_actions

Manage WhatsApp contact blocking and unblocking operations. Handle contact blocking status with action-based operations to control message reception from specific contacts. Contacts are identified by phone number in E.164 format, not by WhatsApp ID.

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": {
      "action": "<action>",
      "device": "<device>",
      "contacts": "<contacts>"
    },
    "name": "manage_whatsapp_contact_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform on WhatsApp contact blocking/unblocking
deviceYesWhatsApp device ID connected to Wassenger (24 character hexadecimal string)
contactsYesArray of contact phone numbers in E.164 format to block or unblock (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully notes that blocking controls message reception and that contacts are identified by phone number rather than WhatsApp ID, but it omits permissions, reversibility, side effects on existing chats, and response behavior for a 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.

Conciseness4/5

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

The description is short and front-loaded, with the core purpose stated immediately. It has some redundancy between 'blocking and unblocking operations' and 'contact blocking status,' but it remains efficient.

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?

For a three-parameter mutation tool with full schema coverage, the description covers purpose and identifier format adequately. However, without annotations or an output schema, it should say more about operational effects, permissions, and whether blocking changes existing conversations.

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 action, device, and contacts. The description reinforces E.164 formatting and clarifies that contacts are not identified by WhatsApp ID, but adds no meaning beyond the schema for device or action parameters.

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 clear resource and operation: WhatsApp contact blocking and unblocking, with action-based control over message reception. It is more specific than the bare tool name, though it does not explicitly contrast itself with sibling tools like manage_whatsapp_contacts.

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 usage by explaining that the tool controls message reception from specific contacts, but it does not state when to use this tool versus manage_whatsapp_contacts or provide any exclusions or prerequisites.

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

All WhatsApp Business API by Wassenger toolsInspect
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