Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

contact_unblock

Unblock a WhatsApp contact by providing the session ID and contact ID. Restore communication with previously blocked contacts.

Instructions

[Contact] Unblock the contact. Unblock the contact from WhatsApp.

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": "contact_unblock"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactIdNoUnique WhatsApp ID for the contact
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but it merely restates the action without disclosing idempotency, session requirements, permissions, or side effects beyond unblocking.

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 description is very short but redundant, repeating 'Unblock the contact' in both sentences; the second sentence adds no new information, making it less concise than it could be.

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?

There is no output schema or annotations, and the description does not explain return values, error behavior, or the relationship to contact_block, leaving a mutation tool insufficiently specified for an agent.

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?

The input schema already describes both contactId and sessionId with examples and coverage at 100%, so the description adds no additional parameter meaning, justifying the baseline score.

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 'Unblock the contact from WhatsApp' with a specific verb and resource, and it is distinct from sibling tools like contact_block, which handles the opposite action.

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?

No guidance is provided on when to use this tool versus alternatives such as contact_block, and there are no exclusions or contextual triggers mentioned.

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