Skip to main content
Glama

Delete Whatsapp Business Member

delete_whatsapp_community_member

Delete a WhatsApp community member. Requires confirm set to DELETE. Business and community refer to the same thing and are interchangeable. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "whatsappId": "<whatsappId>"
    },
    "name": "delete_whatsapp_community_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
whatsappIdYesWhatsApp member record ID.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / whatsappId / description
      Added value: +"WhatsApp member record ID."
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

The description goes well beyond the annotations by disclosing permission gating, a plan-tier restriction, and a mandatory grace-period warning/resubscribe-link flow. The annotations declare destructiveHint=false while the description frames this as a confirmed destructive 'delete', which is odd but is an annotation weakness rather than a description error (readOnlyHint=false is consistent with a write). It does not say what happens to the member record after deletion or whether the action is reversible.

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?

Front-loads the action, then the confirmation requirement, then the access-gating procedure in a logical order. Dense but nearly every sentence carries an operational constraint; the 'business and community are interchangeable' aside could be tightened.

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?

Covers the full pre-flight workflow an agent needs for a gated destructive action: access check, plan restriction, warning display, and blocking conditions. Return behavior is unspecified, but with no output schema and a delete operation that is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns an extra point by pinning the confirm argument to the exact literal DELETE, whereas the schema only offers 'for example DELETE'. It adds nothing about communityId or whatsappId 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?

States a specific verb and resource ('Delete a WhatsApp community member') and clarifies that business/community nomenclature is interchangeable, which removes ambiguity created by sibling names. It does not, however, separate itself from close siblings like remove_community_member or delete_whatsapp_business_member, so an agent still needs to infer which deletion variant applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions: call check_business_tool_access before collecting inputs, FREE businesses are barred regardless of feature rows, and do not proceed when access is blocked. Missing is guidance on choosing this over the adjacent remove_* or delete_whatsapp_business_member tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources